 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| this is information on a product in full production. december 2017 docid027603 rev 4 1/220 ST25DV04K st25dv16k st25dv64k dynamic nfc/rfid tag ic with 4-kbit, 16-kbit or 64-kbit eeprom, and fast transfer mode capability datasheet - production data features i 2 c interface ? two-wire i 2 c serial interface supports 1mhz protocol ? single supply voltage: 1.8v to 5.5v ? multiple byte write programing (up to 256 bytes) contactless interface ? based on iso/iec 15693 ? nfc forum type 5 tag certified by the nfc forum ? supports all iso/iec 15693 modulations, coding, subcarrier modes and data rates ? custom fast read access up to 53 kbit/s ? single and multiple blocks read (same for extended commands) ? single and multiple blocks write (up to 4) (same for extended commands) ? internal tuning capacitance: 28.5 pf memory ? up to 64-kbits of eeprom (depending on version) ? i 2 c interface accesses bytes ? rf interface accesses blocks of 4 bytes ? write time: ? from i 2 c: typical 5ms for 1 byte ? from rf: typical 5ms for 1 block ? data retention: 40 years ? write cycles endurance: ? 1 million write cycles at 25 c ? 600k write cycles at 85 c ? 500k write cycles at 105 c ? 400k write cycles at 125 c fast transfer mode ? fast data transfer between i 2 c and rf interfaces ? half-duplex 256-byte dedicated buffer energy harvesting ? analog output pin to power external components data protection ? user memory: 1 to 4 conf igurable areas, protectable in read and/or write by three 64-bit passwords in rf and one 64-bit password in i 2 c ? system configuration: protected in write by a 64-bit password in rf and a 64-bit password in i 2 c gpo ? interruption pin configurable on multiple rf events (field change, memory write, activity, fast transfer end, user set/reset/pulse) ? open drain or cmos output (depending on version) low power mode (10-ball and 12-pin package only) ? input pin to trigger low power mode rf management ? rf command interpreter enabled/disabled from i 2 c host controller temperature range ? range 6: ? from -40 to 85 c ? range 8: ? from -40 to 105 c (udfpn8 and udfpn12 only) ? from -40 to 125 c (so8n and tssop8 only, 105 c max on rf interface) package ? 8-pin, 10-ball and 12-pin packages ? ecopack2 ? (rohs compliant) so8 tssop8 ufdfpn12 ufdfpn8 wafer wlcsp10 www.st.com
contents ST25DV04K st25dv16k st25dv64k 2/220 docid027603 rev 4 contents 1 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1.1 st25dvxxx block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1.2 st25dvxxx packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2 signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.1 serial link (scl, sda) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.1.1 serial clock (scl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.1.2 serial data (sda) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.2 power control (v cc , lpd,v ss ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.2.1 supply voltage (v cc ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.2.2 low power down (lpd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.2.3 ground (v ss ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.3 rf link (ac0 ac1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.3.1 antenna coil (ac0, ac1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.4 process control (v dcg , gpo) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.4.1 driver supply voltage (v dcg ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.4.2 general purpose output (gpo) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.5 energy harvesting analog output (v_eh) . . . . . . . . . . . . . . . . . . . . . . . . . 21 3 power management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.1 wired interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.2 contactless interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 4 memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.1 memory organization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.2 user memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.2.1 user memory areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 4.3 system configuration area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 4.4 dynamic configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.5 fast transfer mode mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 5 st25dvxxx specific features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 5.1 fast transfer mode (ftm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 docid027603 rev 4 3/220 ST25DV04K st25dv16k st25dv64k contents 7 5.1.1 fast transfer mode registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 5.1.2 fast transfer mode usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 5.2 gpo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 5.2.1 st25dvxxx interrupt capabilit ies on rf events . . . . . . . . . . . . . . . . . . . 44 5.2.2 gpo and power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 5.2.3 gpo registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 5.2.4 configuring gpo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 5.3 energy harvesting (eh) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 5.3.1 energy harvesting registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 5.3.2 energy harvesting feature description . . . . . . . . . . . . . . . . . . . . . . . . . . 60 5.3.3 eh delivery state diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 5.3.4 eh delivery sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 5.4 rf management feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 5.4.1 rf management registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 5.4.2 rf management feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 5.5 interface arbitration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 5.6 data protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 5.6.1 data protection registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 5.6.2 passwords and security sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 5.6.3 user memory protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 5.6.4 system memory protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 5.7 device parameter registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 6i 2 c operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 6.1 i2c protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 6.1.1 start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 6.1.2 stop condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 6.1.3 acknowledge bit (ack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 6.1.4 data input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 6.2 i 2 c timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 6.2.1 i 2 c timeout on start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 6.2.2 i 2 c timeout on clock period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 6.3 device addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 6.4 i 2 c write operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 6.4.1 i 2 c byte write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 6.4.2 i 2 c sequential write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 contents ST25DV04K st25dv16k st25dv64k 4/220 docid027603 rev 4 6.4.3 minimizing system delays by polling on ack . . . . . . . . . . . . . . . . . . . . 92 6.5 i 2 c read operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 6.5.1 random address read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 6.5.2 current address read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 6.5.3 sequential read access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 6.5.4 acknowledge in read mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 6.6 i 2 c password management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 6.6.1 i 2 c present password command description . . . . . . . . . . . . . . . . . . . . . 97 6.6.2 i 2 c write password command description . . . . . . . . . . . . . . . . . . . . . . . 98 7 rf operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 7.1 rf communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 7.1.1 access to a iso/iec 15693 device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 7.2 rf communication and energy harvesting . . . . . . . . . . . . . . . . . . . . . . . 100 7.3 fast transfer mode mailbox access in rf . . . . . . . . . . . . . . . . . . . . . . . 100 7.4 rf protocol description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 7.4.1 protocol description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 7.4.2 st25dvxxx states referring to rf protocol . . . . . . . . . . . . . . . . . . . . . 101 7.4.3 modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 7.4.4 request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 7.4.5 request flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 7.4.6 response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 7.4.7 response flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 7.4.8 response and error code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 7.5 timing definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 7.6 rf commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 7.6.1 rf command code list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 7.6.2 command codes list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 7.6.3 general command rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 7.6.4 inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 7.6.5 stay quiet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 7.6.6 read single block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 7.6.7 extended read single block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 7.6.8 write single block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 7.6.9 extended write single block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 7.6.10 lock block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 docid027603 rev 4 5/220 ST25DV04K st25dv16k st25dv64k contents 7 7.6.11 extended lock block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 7.6.12 read multiple blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 7.6.13 extended read multiple blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 7.6.14 write multiple blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 7.6.15 extended write multiple blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 7.6.16 select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 7.6.17 reset to ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 7.6.18 write afi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 7.6.19 lock afi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 7.6.20 write dsfid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 7.6.21 lock dsfid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 7.6.22 get system info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 7.6.23 extended get system info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 7.6.24 get multiple block security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 7.6.25 extended get multiple block security status . . . . . . . . . . . . . . . . . . . . 142 7.6.26 read configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 7.6.27 write configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 7.6.28 read dynamic configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 7.6.29 write dynamic configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 7.6.30 manage gpo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 7.6.31 write message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 7.6.32 read message length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 7.6.33 read message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 7.6.34 fast read message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 7.6.35 write password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 7.6.36 present password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 7.6.37 fast read single block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 7.6.38 fast extended read single block . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 7.6.39 fast read multiple blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 7.6.40 fast extended read multiple block . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 7.6.41 fast write message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 7.6.42 fast read message length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 7.6.43 fast read dynamic configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 7.6.44 fast write dynamic configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 8 unique identifier (uid) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 contents ST25DV04K st25dv16k st25dv64k 6/220 docid027603 rev 4 9 device parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 9.1 maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 9.2 i 2 c dc and ac parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 9.3 gpo characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 9.4 rf electrical parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 10 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 10.1 so8n package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 10.2 tssop8 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 10.3 ufdfn8 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 10.4 ufdfpn12 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 10.5 wlcsp10 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 11 ordering information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 appendix a bit representation and coding for fast commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 a.1 bit coding using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 a.1.1 high data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 a.1.2 low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 a.2 st25dvxxx to vcd frames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 a.3 sof when using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 a.3.1 high data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 a.3.2 low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 a.4 eof when using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 a.4.1 high data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 a.4.2 low data rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 appendix b i2c sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 b.1 device select codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 b.2 i 2 c byte writing and polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 b.2.1 i 2 c byte write in user memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 b.2.2 i 2 c byte writing in dynamic registers and polling . . . . . . . . . . . . . . . . . 198 b.2.3 i 2 c byte write in mailbox and polling. . . . . . . . . . . . . . . . . . . . . . . . . . . 199 b.2.4 i 2 c byte write and polling in system memory . . . . . . . . . . . . . . . . . . . . 200 b.3 i 2 c sequential writing and polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 docid027603 rev 4 7/220 ST25DV04K st25dv16k st25dv64k contents 7 b.3.1 i 2 c sequential write in user memory and polling . . . . . . . . . . . . . . . . . 202 b.3.2 i 2 c sequential write in mailbox and polling . . . . . . . . . . . . . . . . . . . . . . 204 b.4 i 2 c read current address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 b.4.1 i 2 c current address read in user memory . . . . . . . . . . . . . . . . . . . . . . 205 b.5 i 2 c random address read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 b.5.1 i 2 c random address read in user memory . . . . . . . . . . . . . . . . . . . . . . 206 b.5.2 i 2 c random address read in system memory . . . . . . . . . . . . . . . . . . . 207 b.5.3 i 2 c random address read in dynamic regist ers . . . . . . . . . . . . . . . . . . 207 b.6 i 2 c sequential read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 b.6.1 i 2 c sequential read in user memory . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 b.6.2 i 2 c sequential read in system memory. . . . . . . . . . . . . . . . . . . . . . . . . 210 b.6.3 i 2 c sequential read in dynamic registers . . . . . . . . . . . . . . . . . . . . . . . 211 b.6.4 i 2 c sequential read in mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 b.7 i 2 c password relative sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 b.7.1 i 2 c write password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 b.7.2 i 2 c present password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 list of tables ST25DV04K st25dv16k st25dv64k 8/220 docid027603 rev 4 list of tables table 1. signal names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 table 2. user memory as seen by rf and by i2c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 table 3. maximum user memory block and byte addresses and endai value . . . . . . . . . . . . . . . . 28 table 4. areas and limit calculation from endai registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 5. enda1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 table 6. enda2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 table 7. enda3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 table 8. system configuration memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 9. dynamic registers memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4 table 10. fast transfer mode mailbox memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 table 11. mb_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 table 12. mb_wdg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 13. mb_ctrl_dyn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 table 14. mb_len_dyn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 table 15. field_change when rf is disabled or in sleep mode . . . . . . . . . . . . . . . . . . . . . . . . . . 48 table 16. gpo interrupt ca pabilities in function of rf field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 17. gpo interrupt capabilities in function of vc c power supply. . . . . . . . . . . . . . . . . . . . . . . . 53 table 18. gpo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 table 19. it_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 table 20. gpo_ctrl_dyn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 table 21. it_sts_dyn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 table 22. enabling or disabling gpo interruptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 8 table 23. eh_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 table 24. eh_ctrl_dyn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 table 25. energy harvesting at power-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 table 26. rf_mngt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 table 27. rf_mngt_dyn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 table 28. rfa1ss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 table 29. rfa2ss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 table 30. rfa3ss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 table 31. rfa4ss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 32. i2css . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 table 33. lock_ccfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 table 34. lock_cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 table 35. i2c_pwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 table 36. rf_pwd_0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 37. rf_pwd_1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 38. rf_pwd_2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 table 39. rf_pwd_3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 table 40. i2c_sso_dyn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 41. security session type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 42. lock_dsfid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 table 43. lock_afi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 table 44. dsfid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 table 45. afi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 table 46. mem_size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 table 47. blk_size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 table 48. ic_ref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 docid027603 rev 4 9/220 ST25DV04K st25dv16k st25dv64k list of tables 13 table 49. uid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 table 50. ic_rev . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 table 51. device select code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 table 52. operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 table 53. address most significant byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 table 54. address least significant byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 table 55. st25dvxxx response depending on request_flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 table 56. general request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 table 57. definition of request flags 1 to 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 table 58. request flags 5 to 8 when inventory_flag, bit 3 = 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 table 59. request flags 5 to 8 when inventory_flag, bit 3 = 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 table 60. general response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 table 61. definitions of response flags 1 to 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 table 62. response error code definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 table 63. timing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 table 64. command codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 table 65. inventory request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 table 66. inventory response format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 table 67. stay quiet request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 table 68. read single block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 13 table 69. read single block response format when error_fl ag is not set . . . . . . . . . . . . . . . . . . . 113 table 70. block security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 table 71. read single block response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . 114 table 72. extended read single block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 table 73. extended read single block response format w hen error_flag is not set . . . . . . . . . . . 115 table 74. block security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 table 75. extended read single block response format when error_flag is set . . . . . . . . . . . . . . . 115 table 76. write single block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 table 77. write single block response format when error_ flag is not set . . . . . . . . . . . . . . . . . . . 116 table 78. write single block response format when error_fl ag is set . . . . . . . . . . . . . . . . . . . . . . . 116 table 79. extended write single request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 table 80. extended write single response format when er ror_flag is not set . . . . . . . . . . . . . . . . 117 table 81. extended write single response format when erro r_flag is set . . . . . . . . . . . . . . . . . . . . 118 table 82. lock block request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 table 83. lock block response format when error_flag is no t set . . . . . . . . . . . . . . . . . . . . . . . . . 119 table 84. lock single block response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . 119 table 85. extended lock block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 table 86. extended lock block response format when erro r_flag is not set . . . . . . . . . . . . . . . . . 120 table 87. extended lock block response format when error_ flag is set . . . . . . . . . . . . . . . . . . . . . 120 table 88. read multiple block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 21 table 89. read multiple block response format when erro r_flag is not set. . . . . . . . . . . . . . . . . . 122 table 90. block security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 table 91. read multiple block response format when error_ flag is set . . . . . . . . . . . . . . . . . . . . . . 122 table 92. extended read multiple block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 table 93. extended read multiple block response forma t when error_flag is not set. . . . . . . . . . 123 table 94. block security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 table 95. extended read multiple block response format when error_flag is set . . . . . . . . . . . . . . 123 table 96. write multiple block request forma t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 table 97. write multiple block response format when erro r_flag is not set . . . . . . . . . . . . . . . . . . 125 table 98. write multiple block response format when error_ flag is set . . . . . . . . . . . . . . . . . . . . . . 125 table 99. extended write multiple block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 table 100. extended write multiple block response form at when error_flag is not set. . . . . . . . . . 126 list of tables ST25DV04K st25dv16k st25dv64k 10/220 docid027603 rev 4 table 101. extended write multiple block response format when error_flag is set . . . . . . . . . . . . . . 127 table 102. select request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 table 103. select block response format when error_flag is not set. . . . . . . . . . . . . . . . . . . . . . . . 128 table 104. select response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 table 105. reset to ready request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 table 106. reset to ready response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . 129 table 107. reset to ready response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . 129 table 108. write afi request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 table 109. write afi response format when error_flag is no t set . . . . . . . . . . . . . . . . . . . . . . . . . . 130 table 110. write afi response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 table 111. lock afi request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 table 112. lock afi response format when error_flag is no t set . . . . . . . . . . . . . . . . . . . . . . . . . . 131 table 113. lock afi response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 table 114. write dsfid request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 table 115. write dsfid response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . 132 table 116. write dsfid response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 table 117. lock dsfid request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 table 118. lock dsfid response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . . 134 table 119. lock dsfid response format when error_flag is se t . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 table 120. get system info request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 table 121. get system info response format error_flag is no t set . . . . . . . . . . . . . . . . . . . . . . . . . 135 table 122. memory size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 table 123. get system info response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . 135 table 124. extended get system info request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 table 125. parameter request list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 table 126. extended get system info response format wh en error_flag is not set. . . . . . . . . . . . . 137 table 127. response information flag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 table 128. response other field: st25dvxxx vicc memory si ze . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 table 129. response other field: st25dvxxx ic ref. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 table 130. response other field: st25 dvxxx vicc command list . . . . . . . . . . . . . . . . . . . . . . . . . . 138 table 131. response other field: st25 dvxxx vicc command list byte 1 . . . . . . . . . . . . . . . . . . . . . 138 table 132. response other field: st25 dvxxx vicc command list byte 2 . . . . . . . . . . . . . . . . . . . . . 139 table 133. response other field: st25 dvxxx vicc command list byte 3 . . . . . . . . . . . . . . . . . . . . . 139 table 134. response other field: st25 dvxxx vicc command list byte 4 . . . . . . . . . . . . . . . . . . . . . 140 table 135. extended get system info response format when error_flag is set . . . . . . . . . . . . . . . . . 140 table 136. get multiple block security status request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 table 137. get multiple block security status response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 41 table 138. block security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 table 139. get multiple block security status response format when error_flag is set . . . . . . . . . . . 141 table 140. extended get multiple block security status re quest format . . . . . . . . . . . . . . . . . . . . . . 142 table 141. extended get multiple blo ck security status response format when error_flags not set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 table 142. block security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 table 143. extended get multiple blo ck security status response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 43 table 144. read configuration request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 table 145. read configuration response format when erro r_flag is not set . . . . . . . . . . . . . . . . . . 144 table 146. read configuration response format when error_ flag is set . . . . . . . . . . . . . . . . . . . . . . 144 table 147. write configuration request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 table 148. write configuration response format when error_ flag is not set . . . . . . . . . . . . . . . . . . 145 table 149. write configuration response format when error_fl ag is set . . . . . . . . . . . . . . . . . . . . . . 145 docid027603 rev 4 11/220 ST25DV04K st25dv16k st25dv64k list of tables 13 table 150. read dynamic configuration request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 table 151. read dynamic configuration response format when error_flag is not set. . . . . . . . . . . 146 table 152. read dynamic configuration response format w hen error_flag is set . . . . . . . . . . . . . . . 147 table 153. write dynamic configuration request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 table 154. write dynamic configuration response format when error_flag is not set. . . . . . . . . . . 148 table 155. write dynamic configuration response format wh en error_flag is set . . . . . . . . . . . . . . . 148 table 156. managegpo request format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 table 157. gpoval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 table 158. managegpo response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . 149 table 159. managegpo response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 table 160. write message request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 table 161. write message response format when error_flag is not set. . . . . . . . . . . . . . . . . . . . . . 150 table 162. write message response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . 151 table 163. read message length request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 table 164. read message length response format when er ror_flag is not set . . . . . . . . . . . . . . . 152 table 165. read message length response format when erro r_flag is set . . . . . . . . . . . . . . . . . . . . 152 table 166. read message request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 table 167. read message response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . 153 table 168. write password request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 table 169. write password response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . 155 table 170. write password response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . 155 table 171. present password request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 56 table 172. present password response format when error_fl ag is not set . . . . . . . . . . . . . . . . . . . 156 table 173. present password response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . 157 table 174. fast read single block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 table 175. fast read single block response format when error_flag is not set . . . . . . . . . . . . . . . 158 table 176. block security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 table 177. fast read single block response format when er ror_flag is set . . . . . . . . . . . . . . . . . . . 158 table 178. fast extended read single block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 table 179. fast extended read single block response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 table 180. block security status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 table 181. fast extended read single block response format when error_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 60 table 182. fast read multiple block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 table 183. fast read multiple block response format when error_flag is not set. . . . . . . . . . . . . . 161 table 184. block security status if option_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 table 185. fast read multiple block response format when error_flag is set . . . . . . . . . . . . . . . . . . 161 table 186. fast extended read multiple block request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 table 187. fast extended read multiple block response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 table 188. block security status if option_flag is set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 table 189. fast read multiple block response format when error_flag is set . . . . . . . . . . . . . . . . . . 163 table 190. fast write message request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 64 table 191. fast write message response format when erro r_flag is not set. . . . . . . . . . . . . . . . . . 164 table 192. fast write message response format when error_ flag is set . . . . . . . . . . . . . . . . . . . . . . 164 table 193. fast read message length request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 table 194. fast read message length response format when error_flag is not set . . . . . . . . . . . 166 table 195. fast read message length response format when error_flag is set . . . . . . . . . . . . . . . . 166 table 196. fast read dynamic configuration request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 table 197. fast read dynamic configuration response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 list of tables ST25DV04K st25dv16k st25dv64k 12/220 docid027603 rev 4 table 198. fast read dynamic configuration response format when error_flag is set . . . . . . . . . . . 167 table 199. fast write dynamic configuration request format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 table 200. fast write dynamic configuration response format when error_flag is not set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 table 201. fast write dynamic configuration response format when error_flag is set . . . . . . . . . . . 168 table 202. uid format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 table 203. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 table 204. i 2 c operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 table 205. ac test measurement conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 table 206. input parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 table 207. i 2 c dc characteristics up to 85c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 table 208. i 2 c dc characteristics up to 125c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 table 209. i 2 c ac characteristics up to 85c. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 table 210. i 2 c ac characteristics up to 125c. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 table 211. gpo dc characteristics up to 85c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 79 table 212. gpo dc characteristics up to 125c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 0 table 213. gpo ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 table 214. rf characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 table 215. operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 table 216. so8n ? 8-lead 4.9 x 6 mm, plastic small outline, 150 mils body width, package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 table 217. tssop8 ? 8-lead thin shrink sm all outline, 3 x 6.4 mm, 0.65 mm pitch, package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 table 218. ufdfn8 - 8-lead, 2 3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 table 219. ufdfpn12 - 12-lead, 3x3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat package mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 table 220. wlcsp - 10 balls, 1.649x1.483 mm, 0.4 mm pitch, wafer level chip scale mechanical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 table 221. ordering information scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 table 222. st25dvxxx device select usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 96 table 223. byte write in user memory when write operation allowed . . . . . . . . . . . . . . . . . . . . . . . . 196 table 224. polling during programming after byte writing in user memory. . . . . . . . . . . . . . . . . . . . . 197 table 225. byte write in user memory when write operation is not allowed. . . . . . . . . . . . . . . . . . . . 197 table 226. byte write in dynamic register (if not read only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 table 227. polling during programming after byte write in dynamic register . . . . . . . . . . . . . . . . . . 198 table 228. byte write in dynamic register if read only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 table 229. byte write in mailbox when mailbox is free from rf message and fast transfer mode is activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 table 230. byte write in mailbox when mailbox is not free from rf message fast transfer mode is not activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 table 231. byte write in system memory if i2c security session is open and register is not ro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 00 table 232. polling during programing after byte write in system memory if i 2 c security session is open and register is not ro. . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 table 233. byte write in system memory if i 2 c security session is closed or register is ro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 table 234. sequential write user memory when write operation allowed and all bytes belong to same area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 table 235. polling during programing after sequential write in user memory when write operation allowed and all bytes belong to same area. . . . . . . . . . . . . . . . . . . 202 table 236. sequential write in user memory when write operation allowed docid027603 rev 4 13/220 ST25DV04K st25dv16k st25dv64k list of tables 13 and crossing over area border . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 table 237. polling during programing after sequential write in user memory when write operation allowed and crossing over area border. . . . . . . . . . . . . . . . . . . . . . 204 table 238. sequential write in mailbox when mailbox is free from rf message and fast transfer mode is activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 table 239. polling during programing after sequential write in mailbox . . . . . . . . . . . . . . . . . . . . . . . 205 table 240. current byte read in user memory if read operation allowed (depending on area protection and rf user security session) . . . . . . . . . . . . . . . . . . . . . 205 table 241. current read in user memory if read operation not allowed (depending on area protection and rf user security session) . . . . . . . . . . . . . . . . . . . . . 205 table 242. random byte read in user memory if read operation allowed (depending on area protection and rf user security session) . . . . . . . . . . . . . . . . . . . . . 206 table 243. random byte read in user memory if operation not allowed (depending on area protection and rf user security) . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 table 244. byte read system memory (static register or i2c password after a valid pres ent i2c password) . . . . . . . . . . . . . . . 207 table 245. random byte read in dynamic registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 table 246. sequential read user memory if read operation allowed (depending on area protection and rf user security session) and all bytes belong to the same area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 table 247. sequential read user memory if read operation allowed (depending on area protection and rf user security session) but crossing area border . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 table 248. sequential read user memory if read operation allowed (depending on area protection and rf user security session) . . . . . . . . . . . . . . . . . . . . . 209 table 249. sequential in read system memory (i 2 c security session open if reading i2c_pwd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 0 table 250. sequential read system me mory when access is not granted (i 2 c password i2c_pwd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 table 251. sequential read in dynamic register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 table 252. sequential read in dynamic register and mailbox continuously if fast transfer mode is activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 table 253. sequential in mailbox if fast transfer mode is ac tivated . . . . . . . . . . . . . . . . . . . . . . . . . . 213 table 254. sequential read in mailbox if fast transfer mode is not activated . . . . . . . . . . . . . . . . . . . 214 table 255. write password when i 2 c security session is already open and fast transfer mode is not activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 table 256. write password when i 2 c security session is not open or fast transfer mode activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 table 257. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 list of figures ST25DV04K st25dv16k st25dv64k 14/220 docid027603 rev 4 list of figures figure 1. st25dvxxx block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 figure 2. st25dvxxx 8-pin packages connections with open drain interruption output . . . . . . . . . . 18 figure 3. st25dvxxx 12-pin package connections with cm os interrupt output (gpo). . . . . . . . . . . 19 figure 4. st25dvxxx 10-ball wlcsp package connecti ons with cmos interrupt output (gpo) . . . 19 figure 5. st25dvxxx power-up sequence (no rf field, lpd pin tied to vss or package without lpd pin). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 figure 6. st25dvxxx rf power up sequence (no dc supply) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 figure 7. memory organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 figure 8. st25dvxxx user memory areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 7 figure 9. rf to i 2 c fast transfer mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 figure 10. i 2 c to rf fast transfer mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 figure 11. fast transfer mode mailbox access management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 figure 12. rf_user chronogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 figure 13. rf_activity chronogram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 figure 14. rf_interrupt chronogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 7 figure 15. field_change chronogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 8 figure 16. rf_put_msg chronogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 figure 17. rf_get_msg chronogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 figure 18. rf_write chronogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 figure 19. eh delivery state diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 figure 20. st25dvxxx energy harvesting delivery sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 figure 21. st25dvxxx, arbitration between rf and i 2 c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 figure 22. rf security sessions management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 figure 23. i2c security sessions management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 figure 24. i 2 c bus protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 figure 25. i2c timeout on start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 figure 26. write mode sequences when write is not inhibited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 figure 27. write mode sequences when write is inhibited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 figure 28. write cycle polling flowchart using ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 figure 29. read mode sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 figure 30. i 2 c present password sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 figure 31. i 2 c write password sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 figure 32. st25dvxxx protocol timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 figure 33. st25dvxxx state transition diagra m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2 figure 34. stay quiet frame exchange between vcd and st 25dvxxx . . . . . . . . . . . . . . . . . . . . . . 113 figure 35. read single block frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . 114 figure 36. extended read single block frame exchange between vcd and st25dvxxx . . . . . . . . 115 figure 37. write single block frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . 117 figure 38. extended write single frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . 118 figure 39. lock single block frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . 119 figure 40. extended lock block frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 21 figure 41. read multiple block frame exchange betwee n vcd and st25dvxxx . . . . . . . . . . . . . . . 122 figure 42. extended read multiple block frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 figure 43. write multiple block frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . 125 figure 44. extended write multiple block frame exchange between vcd and st25dvxxx . . . . . . . 127 figure 45. select frame exchange between vcd and st25dvxx x . . . . . . . . . . . . . . . . . . . . . . . . . . 128 docid027603 rev 4 15/220 ST25DV04K st25dv16k st25dv64k list of figures 16 figure 46. reset to ready frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . 129 figure 47. write afi frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . . . . . . 130 figure 48. lock afi frame exchange between vcd and st25dvxxx. . . . . . . . . . . . . . . . . . . . . . . . 132 figure 49. write dsfid frame exchange between vcd and st25dvxxx. . . . . . . . . . . . . . . . . . . . . 133 figure 50. lock dsfid frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . . . . 134 figure 51. get system info frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . 136 figure 52. extended get system info frame exchange between vcd and st25dvxxx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 figure 53. get multiple block security status frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 42 figure 54. extended get multiple block security status frame exchange between vcd and st25dvxxx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 figure 55. read configuration frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . 144 figure 56. write configuration frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . 146 figure 57. read dynamic configuration frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 figure 58. write dynamic configuration frame exchange between vcd and st25dvxxx . . . . . . . . 148 figure 59. managegpo frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . . . 150 figure 60. write message frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . . 151 figure 61. read message length frame exchange between vcd and st25dvxxx. . . . . . . . . . . . . 152 figure 62. read message frame exchange between vcd and st25dvxxx. . . . . . . . . . . . . . . . . . . 153 figure 63. fast read message frame exchange between vcd and st25dvxxx. . . . . . . . . . . . . . . 154 figure 64. write password frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . 156 figure 65. present password frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . 157 figure 66. fast read single block frame exchange between vcd and st25dvxxx . . . . . . . . . . . . 158 figure 67. fast extended read single block frame exchange between vcd and st25dvxxx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 figure 68. fast read multiple block frame exchange between vcd and st25dvxxx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 figure 69. fast extended read multiple block frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 figure 70. fast write message frame exchange between vcd and st25dvxxx . . . . . . . . . . . . . . . 165 figure 71. fast read message length frame exchange between vcd and st25dvxxx. . . . . . . . . 166 figure 72. fast read dynamic configuration frame exchange between vcd and st25dvxxx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 figure 73. fast write dynamic configuration frame exchange between vcd and st25dvxxx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 figure 74. ac test measurement i/o waveform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 figure 75. i 2 c ac waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 figure 76. i 2 c fast mode (f c = 1 mhz): maximum r bus value versus bus parasitic capacitance (c bus ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 figure 77. ask modulated signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 figure 78. so8n ? 8-lead, 4.9 x 6 mm, plastic small outline, 150 mils body width, package outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 figure 79. tssop8 ? 8-lead thin shrink sm all outline, 3 x 6.4 mm, 0.65 mm pitch, package outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 figure 80. ufdfn8 - 8-lead, 2 3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat package outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6 figure 81. ufdfpn12 - 12-lead, 3x3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat package outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 figure 82. wlcsp - 10 balls, 1.649x1.483 mm, 0.4 mm pitch, wafer level chip scale package outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 list of figures ST25DV04K st25dv16k st25dv64k 16/220 docid027603 rev 4 figure 83. wlcsp - 10 balls, 1.649x1.483 mm, 0.4 mm pitch, wafer level chip scale recommended footprint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 figure 84. logic 0, high data rate, fast commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3 figure 85. logic 1, high data rate, fast commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3 figure 86. logic 0, low data rate, fast co mmands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3 figure 87. logic 1, low data rate, fast co mmands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 4 figure 88. start of frame, high data rate, one subcarrier , fast commands. . . . . . . . . . . . . . . . . . . . . 194 figure 89. start of frame, low data rate, one subcarrier , fast commands . . . . . . . . . . . . . . . . . . . . . 194 figure 90. end of frame, high data rate, one subcarrier , fast commands . . . . . . . . . . . . . . . . . . . . . 195 figure 91. end of frame, low data rate, one subcarrier, fast commands . . . . . . . . . . . . . . . . . . . . . . 195 docid027603 rev 4 17/220 ST25DV04K st25dv16k st25dv64k description 219 1 description the ST25DV04K, st25dv16k and st25dv64k devices are nfc rfid tags offering respectively 4 kbit, 16 kbit, and 64 kbit of electrically eras able programmable memory (eeprom). ST25DV04K, st25dv16k and st25dv64k offer two interfaces. the first one is an i 2 c serial link and can be operated from a dc power supply. the second one is a rf link activated when ST25DV04K, st25dv16k or st25dv64k act as a contactless memory powered by the received carrier electromagnetic wave. in i 2 c mode, the ST25DV04K, st25dv16k and st25dv64k user memory contains up to 512 bytes, 2048 bytes and 8192 bytes, which co uld be split in 4 flexible and protectable areas. in rf mode, following iso/iec 15693 or nfc forum type 5 recommendations, ST25DV04K, st25dv16k and st25dv64k user memory cont ains respectively up to 128 blocks, 512 blocks and 2048 blocks of 4 bytes which could be split in 4 flexible and protectable areas. ST25DV04K, st25dv16k and st25dv64k offer a fast transfer mode between the rf and contact worlds, thanks to a 256 bytes volatile buffer (also ca lled mailbox). in addition, the gpo pin of the ST25DV04K, st25dv16k a nd st25dv64k provide data informing the contact world about incoming events, like rf fi eld detection, rf activity in progress or mailbox message availability. an energy harvesting f eature is also propo sed when external conditions make it possible. herein after all concerned devices that are ST25DV04K, st25dv16k and st25dv64k are mentioned to as st25dvxxx. 1.1 st25dvxxx block diagram figure 1. st25dvxxx block diagram 1. v dcg and lpd are included in 12 pins package only / 3 ' $ & $ & 9 b ( + 9 ' & * * 3 2 9 f f 6 ' $ 6 & / 9 v v 9 9 2 / 7 $ * ( 5 ( * 8 / $ 7 2 5 5 ) , 1 7 ( 5 ) $ & ( s ) w x q l q j f d s d f l w d q f h 8 s w r . e l w v 8 v h u p h p r u \ % \ w h v % 8 ) ) ( 5 , 6 2 , ( & 3 5 2 7 2 & 2 / $ 1 ' & 2 1 7 5 2 / 0 ( 0 2 5 < & 2 1 7 5 2 / ' , * , 7 $ / 8 1 , 7 & 2 1 7 5 2 / ( 1 ( 5 * < + $ 5 9 ( 6 7 , 1 * & 2 1 7 5 2 / ) $ 6 7 7 5 $ 1 6 ) ( 5 & 2 1 7 5 2 / $ 1 $ / 2 * ) 5 2 1 7 ( 1 ' ( 1 ( 5 * < + $ 5 9 ( 6 7 , 1 * , & , 1 7 ( 5 ) $ & ( , & & 2 1 7 5 2 / ( ( 3 5 2 0 6 \ v w h p u h j l v w h u v ' \ q d p l f u h j l v w h u v 0 6 y 9 description ST25DV04K st25dv16k st25dv64k 18/220 docid027603 rev 4 1.2 st25dvxxx packaging st25dvxxx is provided in different packages: ? 8 pins (s08n or tsspop8 or ufdfpn8) for the open drain version of interrupt output ? 10 balls (wlcsp) and 12 pins (ufdfpn12) for a cmos interrupt output. this package includes an additional element t hat minimizes stan dby consumption. figure 2. st25dvxxx 8-pin packages connections with open drain interruption output 1. exposed pad is only present on ufdfpn8 package. table 1. signal names signal name function direction v_eh energy harvesting power output gpo interrupt output output sda serial data i/o scl serial clock input ac0, ac1 antenna coils v cc supply voltage power v ss ground lpd (1) 1. available only on 10-ball and 12-pin packages. low power down mode input v dcg (1) supply voltage for gpo driver power nc not connected must be left floating ep (2) 2. available only on ufdpn8 and ufdfpn12 packages. exposed pad must be left floating $ & 0 6 y 9 9 b ( + $ & 9 6 6 9 & & * 3 2 2 ' 6 & / 6 ' $ ( 3 docid027603 rev 4 19/220 ST25DV04K st25dv16k st25dv64k description 219 figure 3. st25dvxxx 12-pin package connections with cmos interrupt output (gpo) 1. exposed pad is only present on ufdfpn12 package. figure 4. st25dvxxx 10-ball wlcsp package connections with cmos interrupt output (gpo) 9 b ( + 0 6 y 9 1 & $ & $ & * 3 2 & 0 2 6 9 ' & * 1 & 6 & / / 3 ' 9 & & 9 6 6 6 ' $ ( 3 9 & & 9 ' & * 6 ' $ 6 & / 9 6 6 $ & / 3 ' $ & 9 b ( + * 3 2 $ % & ' ( 0 d u n l q j v l g h w r s y l h z 9 & & 9 ' & * 6 ' $ 6 & / 9 6 6 $ & / 3 ' $ & 9 b ( + * 3 2 $ % & ' ( % x p s v l g h e r w w r p y l h z 0 6 y 9 signal descriptions ST25DV04K st25dv16k st25dv64k 20/220 docid027603 rev 4 2 signal descriptions 2.1 serial link (scl, sda) 2.1.1 serial clock (scl) this input signal is used to strobe all data in and out of the st25dvxxx. in applications where this signal is used by sl ave devices to synchronize the bus to a slower clock, the bus master must have an open drain output, and a pull-up resistor must be connected from serial clock (scl) to v cc . see section 9.2 to know how to calculate the value of this pull-up resistor 2.1.2 serial data (sda) this bidirectional signal is used to transfer data in or out of the st25dvxxx. it is an open drain output that may be wire-or?ed with other open drain or open collector signals on the bus. a pull-up resistor must be connected from serial data (sda) to v cc . ( figure 76 indicates how the value of the pull-up resistor can be calculated). 2.2 power control (v cc , lpd,v ss ) 2.2.1 supply voltage (v cc ) this pin can be connected to an external dc supply voltage. note: an internal voltage regulator allows the external voltage applied on v cc to supply the st25dvxxx, while preventing th e internal power supply (rectified rf waveforms) to output a dc voltage on the v cc pin. 2.2.2 low power down (lpd) this input signal is used to control an internal 1.8 v regulator delivering st25dvxxx internal supply. when lpd is high, this regulator is s hut off and its consumption is reduced below 1a. this regulator has a turn on time in range of 100us, to be added to the boot duration, before the device becomes fully operational. this feature is only available on the 10-ball and 12-pin st25dvxxx package. 2.2.3 ground (v ss ) v ss is the reference for the v cc and v dcg supply voltages and v_eh analog output voltage. docid027603 rev 4 21/220 ST25DV04K st25dv16k st25d v64k signal descriptions 219 2.3 rf link (ac0 ac1) 2.3.1 antenna coil (ac0, ac1) these inputs are used to connec t the st25dvxxx device to an external coil exclusively. it is advised not to connect any other dc or ac path to ac0 or ac1. when correctly tuned, the coil is used to power and access the device using the iso/iec 15693 and iso 18000-3 mode 1 protocols. 2.4 process control (v dcg , gpo) 2.4.1 driver supply voltage (v dcg ) this pin, available only with st25dvxx-jf ve rsion, can be connected to an external dc supply voltage. it only supplies the gpo driver block. st25dvxxx ca nnot be powered by v dcg . if v dcg is left floating, no informa tion will be available on gpo pin. 2.4.2 general purpose output (gpo) the st25dvxxx features a conf igurable output gpo pin used to provide rf activity information to an external device. st25dvxx-ie offers a gpo open drain. this gpo pin must be connected to an external pull-up resistor (> 4.7 k ) to operate. the interrupt consists in pullin g the state to a low level or outputting a low-level pulse on gpo pin. st25dvxx-jf offers a gpo cmos output, which requires to connect v dcg pin to an external power supply. the interrupt consists in setting the state to a high level or outputting a positive pulse on the gpo pin. gpo pin is a configurable output signal, and can mix several interruption modes. by default, the gpo register sets the interruption mode as a rf field change detector. it is able to raise various events like rf activity, memory wr ite completion, or fast transfer actions. it can authorize the rf side to directly drive gpo pin using the manage gpo command to set the output state or emit a single pulse (for example, to wake up an application.). see section 5.2: gpo for details. 2.5 energy harvesting analog output (v_eh) this analog output pin is used to deliver the analog voltage v_eh available when the energy harvesting mode is enabled and if th e rf field strength is sufficient. when the energy harvesting mode is disabled or the rf fi eld strength is not suff icient, v_eh pin is in high-z state (see section 5.3: energy harvesting (eh) for details). energy harvesting voltage output is not regulated. power management ST25DV04K st25dv16k st25dv64k 22/220 docid027603 rev 4 3 power management 3.1 wired interface operating supply voltage v cc in contact mode, prior to sele cting the memory and issuing in structions to it, a valid and stable v cc voltage within the specified [v cc (min), v cc (max)] range must be applied (see table 204: i 2 c operating conditions ). to maintain a stable dc supply voltage, it is recommended to decouple the v cc line with a suitable capacitor (usually of the order of 10 nf and 100 pf) close to the v cc /v ss package pins. this voltage must remain stable and valid unt il the end of the transmission of the instruction and, for a write instruction, until the co mpletion of the internal i2c write cycle (t w ). instructions are not taken in to account until completion of st25dvxxx's boot sequence (see figure 5 ). figure 5. st25dvxxx power-up sequence (no rf field, lpd pin tied to v ss or package without lpd pin) power-up conditions when the power supply is turned on, v cc rises from v ss to v cc . the v cc rise time must not vary faster than 1v/s. device reset in i2c mode in order to prevent inadvertent write operations during power-up, a power-on reset (por) circuit is included. at power -up (continuous rise of v cc ), the st25dvxxx does not respond to any i2c instruction until v cc has reached the power-on reset threshold voltage (this threshold is lower than the minimum v cc operating voltage defined in table 204: i 2 c operating conditions ). when v cc passes over the por threshold, the device is reset and enters the standby power mode. however, the device must not be accessed until v cc has reached a valid and stable v cc voltage within the specified [v cc(min) , v cc(max) ] range and 3 r z h u 8 s e \ 9 f f 1 r 9 f f 9 ' & * 9 f f 3 l q 9 l q w b v x s s o \ , & , & l q w h u i d f h u h d g \ 1 r q h $ f f h v v $ o o r z h g 5 ) r u , & , & 6 w d u w , & 6 w r s 5 ) $ f f h v v q r w d o o r z h g w e r r w : k h q 5 ) ) l h o g l v s u h v h q w e h i r u h 9 & & v h w x s e r r w l v s h u i r u p h g d i w h u 5 ) i l h o g u l v l q j , i / 3 ' s l q i r o o r z 9 & & e h i r u h w r j r h v o r z w e r r w z l o o v w d u w r q o \ z k h q / 3 ' u h d f k w k h o r z o h y h o 0 6 y 9 docid027603 rev 4 23/220 ST25DV04K st25dv16k st 25dv64k power management 219 t_boot time necessary to st25dvxxx set-up has passed. in the version supporting lpd pin, the boot will take place only when lpd goes low. in a similar way, during power-down (continuous decrease in v cc ), as soon as v cc drops below the power-on reset threshold voltage, t he device stops responding to any instruction sent to it, and i 2 c address counter is reset. power-down mode during power-down (continuous decay of v cc ), the device must be in standby power mode (mode reached after decoding a stop condition, assuming that there is no internal write cycle in progress). 3.2 contactless interface device set in rf mode to ensure a proper boot of the rf circuitr y, the rf field must be turned on without any modulation for a minimum period of time t rf_on . before this time, st 25dvxxx will ignore all received rf commands. (see figure 6: st25dvxxx rf powe r up sequence (no dc supply) ). device reset in rf mode to ensure a proper reset of the rf circuitry, the rf field must be turned off (100% modulation) for a minimum t rf_off period of time. the rf access can be temporarily or indefinitely disabled by setting the appropriate value in the rf disable register. figure 6. st25dvxxx rf power up sequence (no dc supply) 5 ) l q w h u i d f h u h d g \ 3 r z h u 8 s e \ 5 ) 1 r 9 f f 9 ' & * * 3 2 & 0 2 6 9 h u v l r q 5 ) i l h o g 9 l q w b v x s s o \ w e r r w * 3 2 5 ) b $ & 7 , 9 , 7 < * 3 2 ) , ( / ' & + $ 1 * ( 5 ( 4 ( 2 ) $ 1 6 ( 2 ) * 3 2 ) , ( / ' & + $ 1 * ( $ 1 ' 5 ) b $ & 7 , 9 , 7 < 5 ) 5 ( 4 8 ( 6 7 5 ) $ 1 6 : ( 5 1 r q h $ f f h v v $ o o r z h g 5 ) r u , & 9 l q w b v x s s o \ 0 6 y 9 w p l q & ' 1 r d q v z h u w r 5 ) 5 h t x h v w l i d q \ , 7 g x u d w l r q memory management ST25DV04K st25dv16k st25dv64k 24/220 docid027603 rev 4 4 memory management 4.1 memory organization overview the st25dvxxx memory is divided in four main memory areas: ? user memory ? dynamic registers ? fast transfer mode buffer ? system configuration area the st25dvxxx user memory can be divided into 4 flexible user areas. each area can be individually read - and/or - write-protected wi th one out of three specific 64-bit password. the st25dvxxx dynamic registers are accessible by rf or i 2 c host and provide dynamic activity status or allow temporary activation or deactivation of some st25dvxxx features. the st25dvxxx also provides a 256 byte fast transfer mode buffer, acting as a mailbox between rf and i 2 c interface, allowing fast data transfer between contact and contactless worlds. finally, the st25dvxxx system config uration area contains static registers to configure all st25dvxxx features, which can be tuned by user. its access is protected by a 64 bit configuration password. this system configuration area also includes read only device information such as ic reference, memory size or ic revision, as well as a 64-bit block that is used to store the 64- bit unique identifier (uid), and the afi (default 00h) and dsfid (default 00h) registers. the uid is compliant with the iso 15693 descri ption, and its value is used during the anticollision sequence (inventory). the uid value is written by st on the production line. the afi register stores the application family identifier. the dsfid regi ster stores the data storage family identifier used in the anticollision algorithm. the system configuration area includes five additional 64-bit blocks that store an i 2 c password plus three rf user area access passwords and a rf configuration password. docid027603 rev 4 25/220 ST25DV04K st25dv16k st25dv64k memory management 219 figure 7. memory organization 4.2 user memory user memory is accessible from both rf contactless interface and i 2 c wired interface. from rf interface, user memory is addressed as blocks of 4 bytes, starting at address 0. rf extended read and write commands can be used to address all st25dvxxx memory blocks. other read and write commands can only address up to block ffh. from i 2 c interface, user memory is addressed as by tes, starting at address 0. device select must set e2 = 0. user memory can be read in continuity. unlike the rf interface, there is no roll-over when the requested address reac hes the end of the memory capacity. $ u h d $ u h d $ u h d $ u h d & & ) l o h ' \ q d p l f u h j l v w h u v ) d v w 7 u d q v i h u 0 r g h % \ w h v e x i i h u 6 w d w l f f r q i l j x u d w l r q u h j l v w h u v ' h y l f h l q i r u p d w l r q 8 , ' $ ) , ' 6 ) , ' 3 d v v z r u g v $ o z d \ v u h d g d e o h 8 v h u p h p r u \ ( ( 3 5 2 0 x s w r . e l w v 3 d v v z r u g s u r w h f w h g 6 \ v w h p f r q i l j x u d w l r q ( ( 3 5 2 0 3 d v v z r u g s u r w h f w h g ' \ q d p l f f r q i l j x u d w l r q d q g d f w l y l w \ v w d w x v ) d v w 7 u d q v i h u 0 r g h p d l o e r [ 0 6 y 9 memory management ST25DV04K st25dv16k st25dv64k 26/220 docid027603 rev 4 table 2: user memory as seen by rf and by i2c shows how memory is seen from rf interface and from i 2 c interface. note: in the factory all blocks of user memory are initialized to 00h. table 2. user memory as seen by rf and by i 2 c rf command (block addressing) user memory i 2 c command (byte addressing) read single block read multiple blocks fast read single block fast read multiple blocks write single block write multiple blocks ext read single block ext read multiple blocks fast ext read single block fast ext read multi. blocks ext write single block ext write multiple blocks rf block (00)00h i 2 c read command i 2 c write command device select e2 = 0 i 2 c byte 0003h i 2 c byte 0002h i 2 c byte 0001h i 2 c byte 0000h rf block (00)01h i 2 c byte 0007h i 2 c byte 0006h i 2 c byte 0005h i 2 c byte 0004h rf block (00)02h i 2 c byte 000bh i 2 c byte 000ah i 2 c byte 0009h i 2 c byte 0008h .... rf block (00)7fh (1) i 2 c byte 01ffh i 2 c byte 01feh i 2 c byte 01fdh i 2 c byte 01fch .... rf block (00)ffh (2) i 2 c byte 03ffh i 2 c byte 03feh i 2 c byte 03fdh i 2 c byte 03fch ext read single block ext read multiple blocks fast ext read single block fast ext read multi. blocks ext write single block ext write multiple blocks rf block 0100h i 2 c byte 0403h i 2 c byte 0402h i 2 c byte 0401h i 2 c byte 0400h .... rf block 01ffh (3) i 2 c byte 07ffh i 2 c byte 07feh i 2 c byte 07fdh i 2 c byte 07fch .... rf block 07ffh (4) i 2 c byte 1fffh i 2 c byte 1ffeh i 2 c byte 1ffdh i 2 c byte 1ffch 1. last block of user memory in ST25DV04K-xx. 2. last block accessible with read singl e block, read multiple blocks, fa st read single bl ock, fast read multiple blocks, write si ngle block and write mult iple blocks rf commands. 3. last block of user memory in st25dv16k-xx. 4. last block of user memory in st25dv64k-xx. docid027603 rev 4 27/220 ST25DV04K st25dv16k st25dv64k memory management 219 4.2.1 user memory areas the user memory can be split into different ar eas, each one with a distinct access privilege. rf and i 2 c read and write commands are legal only within a same zone: ? in rf, a multiple read or a multiple write command is not executed and returns the error code 0fh if addresses cross the area borders. ? in i 2 c, a read data always return ffh after crossing an area border. a write command is not acknowledged and not executed if the command crosses the area border. each user memory area is defined by its ending block address enda i . the starting block address is defined by the end of the preceding area. there are three enda i registers in the configuration system memory, used to define the end block addresses of area 1, area 2 and area 3. t he end of area 4 is always the last block of memory and is not configurable. figure 8. st25dvxxx user memory areas on factory delivery all enda i are set to maximum value, only area1 exists and includes the full user memory. a granularity of 8 blocks (32 bytes) is offered to co de area ending points. an area?s end limit is coded as followed in enda i registers: ? last rf block address of area = 8 x enda i + 7 => enda i = int(last area i rf block address / 8) ? last i 2 c byte address of area = 32 * enda i + 31 => enda i = int(last area i i 2 c byte address / 32) ? as a consequence, enda1 = 0 means size of area 1 is 8 blocks (32 bytes). $ u h d % o r f n v % \ w h v p l q l p x p $ u h d $ u h d $ u h d 6 7 ' 9 x v h u p h p r u \ ( 1 ' $ ( 1 ' $ ( 1 ' $ $ u h d v o l p l w u h j l v w h u v % o r f n % \ w h k / d v w % o r f n % \ w h r i x v h u p h p r u \ 0 6 y 9 memory management ST25DV04K st25dv16k st25dv64k 28/220 docid027603 rev 4 organization of user memory in areas have the following characteristics: ? at least one area exists (area1), starting at block/byte address 0000h and finishing at enda1, with enda1 = enda2 = enda3 = end of user memory (factory setting). ? two areas could be defined by setting enda1 < enda2 = enda3 = end of user memory. ? three areas may be defined by setting enda1 < enda2 < enda3 = end of user memory. ? a maximum of four areas may be defined by setting enda1 < enda2 < enda3 < end of user memory. ? area 1 specificities ? start of area1 is always block/byte address 0000h. ? area1 minimum size is 8 blocks (32 bytes) when enda1 = 00h. ? area1 is always readable. ? the last area always finishes on the la st user memory block/byte address (enda4 doesn't exist). ? all areas are contiguous: end of area(n) + one block/byte address is always start of area(n+1). area size programming rf user must first open the rf configuratio n security session to write endai registers. i 2 c host must first open i 2 c security session to write endai registers. table 3. maximum user memory block and byte addresses and enda i value device last user memory block address seen by rf last user memory byte address seen by i 2 c maximum enda i value ST25DV04K-xx 007fh 01ffh 0fh st25dv16k-xx 01ffh 07ffh 3fh st25dv64k-xx 07ffh 1fffh ffh table 4. areas and limit calculation from enda i registers area seen from rf interface seen from i 2 c interface area 1 block 0000h ? block (enda1*8)+7 byte 0000h ? byte (enda1*32)+31 area 2 block (enda1+1)*8 ? block (enda2*8)+7 byte (enda1+1)*32 ? byte (enda2*32)+31 area 3 block (enda2+1)*8 ? block (enda3*8)+7 byte (enda2+1)*32 ? byte (enda3*32)+31 area 4 block (enda3+1)*8 ? last memory block byte (enda3+1)*32 ? last memory byte docid027603 rev 4 29/220 ST25DV04K st25dv16k st25dv64k memory management 219 when programming an endai register, t he following rule must be respected: ? endai-1 < endai endai+1 = end of memory. this means that prior to programming any endai register, its successor (endai+1) must first be programmed to the last block/byte of memory: ? successful enda3 programming condition: enda2 < enda3 end of user memory ? successful enda2 programming condition: enda1 < enda2 enda3 = end of user memory ? successful enda1 programming condition: enda1 enda2 = enda 3 = end of user memory if this rule is not respected, an error 0fh is returned in rf, noack is returned in i2c, and programming is not done. in order to respect this rule, the following procedure is recommended when programming areas size (even for changing only one area size): 1. ends of areas 3 and 2 must first be set to the end of memory while respecting the following order: a) if enda3 end of user memory, then set enda3 = end of memory; else, do not write enda3. b) if enda2 end of user memory, then set enda2 = end of memory; else, do not write enda2. 2. then, desired area limits can be set respecting the following order: a) set new enda1 value. b) set new enda2 value, with enda2 > enda1 c) set new enda3 value, with enda3 > enda2 example of successive user memory area setting (for a st25dv64k-xx): 1. initial state, 2 areas are defined: a) enda1 = 10h (last block of area 1: (10h x 8) + 7 = 0087h) b) enda2 = ffh (last block of area 2: (ffh x 8) + 7 = 07ffh) c) enda3 = ffh (no area 3) ? area 1 from block 0000h to 0087h (136 blocks) ? area 2 from block 0088h to 07ffh (1912 blocks) ? there is no area 3. ? there is no area 4. memory management ST25DV04K st25dv16k st25dv64k 30/220 docid027603 rev 4 programming enda3 to ffh in step 2.a would hav e resulted in into an error, since rule endai-1 < endai would not been respec ted (enda2 = enda3 in that case). registers for user memory area configuration 2. split of user memory in four areas: a) enda3 is not updated as it is already set to end of memory. b) enda2 is not updated as it is already set to end of memory. c) set enda1 = 3fh (last block of area 1: (3fh x 8) + 7 = 01ffh) d) set enda2 = 5fh (last block of area 1: (5fh x 8) + 7 = 02ffh) e) set enda3 = bfh (last block of area 1: (bfh x 8) + 7 = 05ffh) ? area1 from block 0000 h to 01ffh (512 blocks) ? area2 from block 0200 h to 02ffh (256 blocks) ? area3 from block 0300 h to 05ffh (768 blocks) ? area4 from block 0600 h to 07ffh (512 blocks). 3. return to a split in two equal areas: a) set enda3 = ffh b) set enda2 = ffh c) set enda1 = 7fh (last block of area 1: (7fh x 8) + 7 = 03ffh) ? area1 from block 0000h to 03ffh (1024 blocks) ? area2 from block 0400h to 07ffh (1024 blocks) ? there is no area3. ? there is no area4. table 5. enda1 (1) rf command read configuration (cmd code a0h) @05h write configuration (cmd code a1h) @05h type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2 = 1, 0005h type r always, w if i 2 c security session is open bit name function factory value b7-b0 enda1 end area 1 = 8*enda1+7 when expressed in blocks (rf) end area 1 = 32*enda1+31 when expressed in bytes (i 2 c) ST25DV04K-xx: 0fh st25dv16k-xx: 3fh st25dv64k-xx: ffh 1. refer to table 8: system configuration memory map for the enda1 register. docid027603 rev 4 31/220 ST25DV04K st25dv16k st25dv64k memory management 219 4.3 system conf iguration area in addition to eeprom user memory, st25dvxxx includes a set of stat ic registers located in the system configuration area memory (eep rom nonvolatile registers). those registers are set during device configuration (i.e.: area extension), or by the application (i.e.: area protection). static registers content is re ad during the boot sequence and define basic st25dvxxx behavior. in rf, the static registers located in the system configuration area can be accessed via dedicated read configuration and write config uration commands, with a pointer acting as the register address. the rf configuration security session must first be open, by presenting a valid rf configuration password, to grant write a ccess to system configuration registers. the system configuration area write access by rf can also be deactivated by i 2 c host. table 6. enda2 (1) rf command read configuration (cmd code a0h) @07h write configuration (cmd code a1h) @07h type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2 = 1, 0007h type r always, w if i 2 c security session is open bit name function factory value b7-b0 enda2 end area 2 = 8 x enda2 + 7 when expressed in blocks (rf) end area 2 = 32*enda2 + 31 when expressed in bytes (i 2 c) ST25DV04K-xx: 0fh st25dv16k-xx: 3fh st25dv64k-xx: ffh 1. refer to table 8: system configuration memory map for the enda2 register. table 7. enda3 (1) rf command read configuration (cmd code a0h) @09h write configuration (cmd code a1h) @09h type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2 = 1, 0009h type r always, w if i 2 c security session is open bit name function factory value b7-b0 enda3 end area 3 = 8 x enda3 + 7 when expressed in blocks (rf) end area 3 = 32 x enda3 + 31 when expressed in bytes (i 2 c) ST25DV04K-xx: 0fh st25dv16k-xx: 3fh st25dv64k-xx: ffh 1. refer to table 8: system configuration memory map for the enda3 register. memory management ST25DV04K st25dv16k st25dv64k 32/220 docid027603 rev 4 in i 2 c static registers located in the system configuration area can be accessed with i 2 c read and write commands with device select e2 =1. readable system areas could be read in continuity. i 2 c security session must first be open, by presenting a valid i 2 c password, to grant write access to system configuration registers. table 8 shows the complete map of the system c onfiguration area, as seen by rf and i 2 c interface. table 8. system configuration memory map rf access static register i 2 c access address type name function device select address type 00h rw (1) table 18: gpo enable/disable its on gpo e2=1 0000h rw (2) 01h rw (1) table 19: it_time interruption pulse duration e2=1 0001h rw (2) 02h rw (1) table 23: eh_mode energy harvesting default strategy after power on e2=1 0002h rw (2) 03h rw (1) table 26: rf_mngt rf interface state after power on e2=1 0003h rw (2) 04h rw (1) table 28: rfa1ss area1 rf access protection e2=1 0004h rw (2) 05h rw (1) table 5: enda1 area 1 ending point e2=1 0005h rw (2) 06h rw (1) table 29: rfa2ss area2 rf access protection e2=1 0006h rw (2) 07h rw (1) table 6: enda2 area 2 ending point e2=1 0007h rw (2) 08h rw (1) table 30: rfa3ss area3 rf access protection e2=1 0008h rw (2) 09h rw (1) table 7: enda3 area 3 ending point e2=1 0009h rw (2) 0ah rw (1) table 31: rfa4ss area4 rf access protection e2=1 000ah rw (2) no access table 32: i2css area 1 to 4 i 2 c access protection e2=1 000bh rw (2) n/a r (3) w (4) table 33: lock_ccfile blocks 0 and 1 rf write protection e2=1 000ch rw (2) 0dh rw (1) table 11: mb_mode fast transfer mode state after power on e2=1 000dh rw (2) 0eh rw (1) table 12: mb_wdg maximum time before the message is automatically released e2=1 000eh rw (2) 0fh rw (1) table 34: lock_cfg protect rf write to system configuration registers e2=1 000fh rw (2) n/a wo (5) table 42: lock_dsfid dsfid lock status e2=1 0010h ro na wo (6) table 43: lock_afi afi lock status e2=1 0011h ro n/a rw (5) table 44: dsfid dsfid value e2=1 0012h ro docid027603 rev 4 33/220 ST25DV04K st25dv16k st25dv64k memory management 219 n/a rw (6) table 45: afi afi value e2=1 0013h ro n/a ro table 46: mem_size memory size value in blocks, 2 bytes e2=1 0014h to 0015h ro ro table 47: blk_size block size value in bytes e2=1 0016h ro n/a ro table 48: ic_ref ic reference value e2=1 0017h ro na ro table 49: uid unique identifier, 8 bytes e2=1 0018h to 001fh ro no access table 50: ic_rev ic revision e2=1 0020h ro - st reserved e2=1 0021h ro - st reserved e2=1 0022h ro - st reserved e2=1 0023h ro table 35: i2c_pwd i 2 c security session password, 8 bytes e2=1 0900h to 0907h r (7) / w (8) n/a wo (9) table 36: rf_pwd_0 rf configuration security session password, 8 bytes no access n/a wo (9) table 37: rf_pwd_1 rf user security session password 1, 8 bytes n/a wo (9) table 38: rf_pwd_2 rf user security session password 2, 8 bytes n/a wo (9) table 39: rf_pwd_3 rf user security session password 3, 8 bytes 1. write access is granted if rf configuration secu rity session is open and c onfiguration is not locked (lock_cfg register equals to 0). 2. write access if i 2 c security session is open. 3. lock_ccfile content is only reada ble through reading the block security status of blocks 00h and 001h (see section 5.6.3: user memory protection ) 4. write access to bit 0 if block 00h is not already locked and to bit 1 if block 01h is not already locked. 5. write access if dsfid is not locked 6. write access if afi is not locked. 7. read access is granted if i 2 c security session is open. 8. write access with i 2 c write password command, only after presenting a correct i 2 c password. 9. write access only if corresponding rf security session is open. table 8. system configuration memory map (continued) rf access static register i 2 c access address type name function device select address type memory management ST25DV04K st25dv16k st25dv64k 34/220 docid027603 rev 4 4.4 dynamic configuration st25dv has a set of dynamic registers that allow temporary modification of its behavior or report on its activity. dynamic registers are vola tile and not restored to their previous values after por. some static registers have an image in dyna mic registers: dynamic register value is initialized with the static register value and may be updated by the application to modify the device behavior temporarily (i.e.: set reset of energy harvesting). when a valid change occurs in a static register, in rf or i 2 c, the corresponding dynamic register is automatically updated. other, dynamic registers, automatically updated, contain indication on st25dv activity. (i.e.: it_sts_dyn gives the interruption?s status or mb_ctrl_dyn gives the fast transfer mode mailbox control). in rf, dynamic registers can be accessed vi a dedicated (fast) read dynamic configuration and (fast) write dynamic configuration commands , with a pointer acting as the register address. no password is needed to access dynamic registers. in i 2 c, dynamic registers can be accessed with i 2 c read and write commands with device select e2=0. dynamic registers can be read in continuity. dynamic registers and fast transfer mode mailbox can be read in continuity, but not written in continuity. no password is needed to access dynamic registers. table 9 shows the complete map of dynamic registers, as seen by rf interface and by i 2 c interface. table 9. dynamic registers memory map rf access dynamic registers i 2 c access address type name function device select address type 00h ro table 20: gpo_ctrl_dyn gpo control e2 = 0 2000h r/w no access - st reserved e2 = 0 2001h ro 02h r/w table 24: eh_ctrl_dyn energy harvesting management & usage status e2 = 0 2002h r/w no access table 27: rf_mngt_dyn rf interface usage management e2 = 0 2003h r/w table 40: i2c_sso_dyn i 2 c security session status e2 = 0 2004h ro table 21: it_sts_dyn interruptions status e2 = 0 2005h ro 0dh r/w table 13: mb_ctrl_dyn fast transfer mode control and status e2 = 0 2006h r/w na ro table 14: mb_len_dyn length of fast transfer mode message e2 = 0 2007h ro docid027603 rev 4 35/220 ST25DV04K st25dv16k st25dv64k memory management 219 4.5 fast trans fer mode mailbox st25dvxxx fast transfer mode uses a dedicated mailbox buffer for transferring messages between rf and i 2 c worlds. this mailbox contains up to 256 bytes of data which are filled from the first byte. fast transfer mode mailbox is accessed in bytes from both rf and i 2 c. in rf, mailbox is read via a dedicated (fast) read message command. read can start from any address value inside the mailbox, between 00h and ffh. writing in the mailbox is done via the (fast) write message command in one shot, always starting at mailbox address 00h. no password is needed to access mailbox from rf, but fast transfer mode must be enabled. in i 2 c, mailbox read can start from any address value between 2008h and 2107h. write mailbox must start from address 2008h to a max of 2107h. no password is needed to access mailbox from i 2 c, but fast transfer mode must be enabled. table 10 shows the map of fast transfer mode mailbox, as seen by rf interface and by i 2 c interface. table 10. fast transfer mode mailbox memory map rf access fast transfer mode buffer i 2 c access address type name function device select address type 00h r/w mb_dyn byte 0 fast transfer mode buffer (256-bytes) e2 = 0 2008h r/w 01h r/w mb_dyn byte 1 e2 = 0 2009h r/w ? ? ? e2 = 0 ... ... feh r/w mb_dyn byte 254 e2 = 0 2106h r/w ffh r/w mb_dyn byte 255 e2 = 0 2107h r/w st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 36/220 docid027603 rev 4 5 st25dvxxx specific features st25dvxxx offers the following features: ? a fast transfer mode (ftm), to achieve a fast link between rf and contact worlds, via a 256 byte buffer called mailbox. this mailbox dynamic buffer of 256 byte can be filled or emptied via either rf or i 2 c. ? a gpo pin, which indicates incoming event to the contact side, like rf field changes, rf activity in progress, rf writing co mpletion or mailbox message availability. ? an energy harvesting element to deliver w of power when external conditions make it possible. ? rf management, which allows st25dvxxx to ignore rf requests. all these features can be programmed by sett ing static and/or dynamic registers of the st25dvxxx. st25dvxxx can be partially custom ized using configuration registers located in the e 2 system area. these registers are: ? dedicated to data memory organization and protection enda i , i2css, rfaiss, lock_ccfile. ? dedicated to fast transf er mode mb_wdg, mb_mode ? dedicated to observat ion, gpo, it_time ? dedicated to rf , rf_mngt, eh_mode ? dedicated the device?s structure lock_cfg a set of additional registers allows to iden tify and customize the product (dsfid, afi, ic_ref, etc.). in i2c, read accesses to the static configuration regist er is always allowed, except for passwords. for dedicated registers, write ac cess is granted after prior successful presentation of the i 2 c password. configuration register are located fr om @00h to 0fh in the system area (device code 111) in rf dedicated commands read configuration and wr ite configuration must be used to access the static configuration registers. update is only possible when the access right was granted by presenting the rf configuration password (rf_pwd_0), and if the system configuration was not previously locked by the i 2 c host (lock_cfg=1), which acts as security master. after any valid write access to the static c onfiguration registers, th e new configuration is immediately applied. some of the static registers have a dynamic image (notice _dyn) preset with the static register value: gpo_ctrl_dyn, eh_ctr l_dyn, rf_mngt_dyn and mb_ctrl_dyn. when it exists, st25dvxxx uses the dynam ic configuration register to manage its processes. a dynamic configuration register updated by the application will recover its default static value after a power on reset (por). docid027603 rev 4 37/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 other dynamic registers are dedicated to process monitoring: ? i2c_sso_dyn is dedicated to data memory protection ? mb_len_dyn, mb_ctrl_dyn are dedicated to fast transfer mode ? it_sts_dyn is dedi cated to interrupt in i 2 c, read and write of the dynamic registers is done using usual i 2 c read & write command at dedicated address. (e2 =0 in device select). in rf read or write accesses to the dynami c registers are associated to the dedicated commands, read dynamic configuration, writ e dynamic configuration and read message length. 5.1 fast trans fer mode (ftm) 5.1.1 fast transfer mode registers static registers table 11. mb_mode (1) rf command read configuration (cmd code a0h) @0dh write configuration (cmd code a1h) @0dh type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2=1, 000dh type r always, w if i 2 c security session is open bit name function factory value b0 mb_mode 0: enabling fast transfer mode is forbidden. 1: enabling fast transfer mode is authorized. 0b b7-b1 rfu - 0000000b 1. refer to table 8: system configuration memory map for the mb_mode register. st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 38/220 docid027603 rev 4 dynamic registers table 12. mb_wdg (1) rf command read configuration (cmd code a0h) @0eh write configuration (cmd code a1h) @0eh type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2=1, 000eh type r always, w if i 2 c security session is open bit name function factory value b2-b0 mb_wdg if mb_wdg = 0, then watchdog duration is infinite 111b b7-b3 rfu - 00000b 1. refer to table 8: system configuration memory map for the mb_wdg register. watch dog duration = 2 mb_wdg 1 ? () 30ms 6 table 13. mb_ctrl_dyn (1) rf command read dynamic configuration (cmd code adh) @0dh fast read dynamic configuration (cmd code cdh) @0dh write dynamic configuration (cmd code aeh) @0dh fast write dynamic configuration (cmd code ceh) @0dh type b0: r always, w ? b7-b1: ro i 2 c address e2 = 0, 2006h type b0: r always, w - b7 - b1: ro bit name function factory value b0 mb_en (2) 0: disable ftm, ftm mailbox is empty 1: enable ftm 0b b1 host_put_msg 0: no i 2 c message in ftm mailbox 1: i 2 c has put a message in ftm mailbox 0b b2 rf_put_msg 0: no rf message in ftm mailbox 1: rf has put message in ftm mailbox 0b docid027603 rev 4 39/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 5.1.2 fast transfer mode usage st25dv acts as mailbox between rf (reader, smartphone, ...) and an i 2 c host (microcontroller...). each interface can send a message containing up to 256 bytes of data to the other interface through that mailbox. to send data from rf reader to i 2 c host, fast transfer mode must be enabled, the mailbox must be free, and the rf user must first writ es the message containing data in the mailbox. b3 rfu - 0b b4 host_miss_msg 0: no message missed by i 2 c 1: i 2 c did not read rf message before watchdog time out 0b b5 rf_miss_msg 0: no message missed by rf 1: rf did not read message before watchdog time out 0b b6 host_current_msg 0: no message or message not coming from i 2 c 1: current message in ft m mailbox comes from i 2 c 0b b7 rf_current_msg 0: no message or message not coming from rf 1: current message in ft m mailbox comes from rf 0b 1. refer to table 9: dynamic registers memory map for the mb_ctrl_dyn register. 2. mb_en bit is automatically reset to 0 if mb_mode register is reset to 0. table 13. mb_ctrl_dyn (1) (continued) rf command read dynamic configuration (cmd code adh) @0dh fast read dynamic configuration (cmd code cdh) @0dh write dynamic configuration (cmd code aeh) @0dh fast write dynamic configuration (cmd code ceh) @0dh type b0: r always, w ? b7-b1: ro i 2 c address e2 = 0, 2006h type b0: r always, w - b7 - b1: ro bit name function factory value table 14. mb_len_dyn (1) rf command read message lenght (cmd code abh) fast read message lenght (cmd code cbh) type ro i 2 c address e2 = 0, 2007h type ro bit name function factory value b7-b0 mb_len size in byte of message contained in ftm mailbox (automatically set by st25dvxxx) 0h 1. refer to table 9: dynamic registers memory map for the mb_len_dyn register. st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 40/220 docid027603 rev 4 i 2 c host is then informed (by interruption on gpo output or polling on mb_ctrl_dyn register) that a message from rf is present in the mailbox. once the complete message has been read by i 2 c, mailbox is considered free again and is available for receiving a new message (data is not cleared). the rf user is informed that the message has been read by the i 2 c host by polling on mb_ctrl_dyn register. figure 9. rf to i 2 c fast transfer mode operation to send data from the i 2 c host to the rf reader, fast transfer mode must be enabled, the mailbox must be free and the i2c host must first write the message containing data in the mailbox. the rf user must poll on mb_ctrl_dyn register to check for the presence of a message from i 2 c in the mailbox. once the complete message has been read by rf user, mailbox is considered free again and is available for receiving a new message (data is not cleared). the i 2 c host is informed that message has been read by rf user through a gpo interruption or by polling on the mb_ctrl_dyn register. , & k r v w 6 7 ' 9 ) d v w 7 u d q v i h u 0 r g h p d l o e r [ % \ w h v ' \ q d p l f u h j l v w h u v 0 % b / ( 1 b ' \ q 0 % b & 5 7 / b ' \ q 6 w d w l f u h j l v w h u v 0 % b 0 2 ' ( 0 % b : ' * , 6 2 , ( & u h d g h u , & * 3 2 5 ) b 3 8 7 b 0 6 * 5 ) p h v v d j h 0 e v n e v 0 6 y 9 docid027603 rev 4 41/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 figure 10. i 2 c to rf fast transfer mode operation v cc supply source is mandatory to activate this feature. no precedence rule is applied: the first request is served first. adding a message is only possible when fast transfer mode is enabled (mb_en=1) and mailbox is free (host_put_msg and rf_put_m sg cleared, which is the case after por or after complete reading of i 2 c message by rf, and complete reading of rf message by i 2 c). a watchdog limits the message av ailability in time: when a time -out occurs, the mailbox is considered free, and the host_miss_msg or rf_miss_msg bits is set into mb_ctrl_dyn register. the data contained in the mailbox is not cleared after a read or after the watchdog has been tr iggered: message data is still av ailable for read and until fast transfer mode is disabled. host_curr ent_msg and rf_current_msg bits are indicating the source of the current data. the message is stored in a buffer (256 bytes), and the write operation is done immediately. . caution: the data written in us er or system memory ( eeprom), eith er from i 2 c or from rf, transits via the 256-bytes fast transfer mode's buffer. consequently fast transfer mode must be deactivated (mb_en=0) before starting any write operation in user or system memory, otherwise command will be notack for i 2 c or get an answer 0fh for rf and programming is not done. i 2 c access to mailbox the access by i 2 c can be done by dedicated address mapping to mailbox (2008h to 2107h) with device identifier e2 = 0. i 2 c reading operation does not support rollover. therefore data out is set to ffh when the counter reaches the message end. the rf_put_msg is cleared after reaching the stop consecutive to reading the last message byte, and the mailbox is considered free (but the message is not cleared and it is still present in the mailbox). , & k r v w 6 7 ' 9 ) d v w 7 u d q v i h u 0 r g h p d l o e r [ % \ w h v ' \ q d p l f u h j l v w h u v 0 % b / ( 1 b ' \ q 0 % b & 5 7 / b ' \ q 6 w d w l f u h j l v w h u v 0 % b 0 2 ' ( 0 % b : ' * , 6 2 , ( & u h d g h u , & * 3 2 5 ) b * ( 7 b 0 6 * + r v w p h v v d j h 0 e v 8 s w r n e v 0 6 y 9 st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 42/220 docid027603 rev 4 a i 2 c reading operation will never clear host _put_msg, and the message remains available for rf. an i 2 c read can start at any address inside the mailbox (between address 2008h and 2107h). a i 2 c write operation must start from the firs t mailbox location, at address 2008h. after reaching the mailbox border at address 2107h all bytes are nack and the command is not executed (rollover feature not supported). at the end of a successful i 2 c message write, the message leng th is automatically set into mb_len_dyn register, and host_put_msg bi t is set into mb_ctrl_dyn register, and the write access to the mailb ox is not possible until the mailbox has been released again. rf access to mailbox the rf control & access to mailbox is possible using dedicated custom commands: ? read dynamic configuration and fast read dynamic configuration to check availability of mailbox. ? write dynamic configuration and fast write dynamic configuration to enable or disable fast transfer mode. ? read message length and fast read message length to get the length of the contained message, ? read message and fast read message to download the content of the mailbox, ? write message and fast write message to put a new message in mailbox. (new length is automatically updated after completion of a successful write message or fast write message command). host_put_msg is cleared following a valid reading of the last message byte, and mailbox is considered free (but message is not cleared and is still present in the mailbox). a rf read can start at any address of inside the message, but return an error 0fh if trying to read after the last byte of the message. a rf reading operation will never clear rf_p ut_msg , the message will remain available for i 2 c. at the end of a successful rf message write, the message length is automatically set in mb_len_dyn register, and rf_put_msg bit is set in mb_ctrl_dyn register. and write access to the mailbox is not possible until mailbox has been freed again. the presence of a dc supply is mandatory to get rf access to the mailbox. vcc_on can be checked reading the dyna mic register eh_ctrl_dyn. to get more details about sequences to prepar e and initiate a fast transfer, to detect progress of a fast transfer or to control and execute a fast transfer, please refer to an4910. how to exchange data between wired (i 2 c) and wireless world (rf iso15693) using fast transfer mode supported by st25dvxxx). docid027603 rev 4 43/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 figure 11. fast transfer mode mailbox access management. note: assuming mb_mode=01h assuming no error occurred : d w f k g r j w u l j , & u h d g i x o o p v j 5 ) u h d g i x o o p v j , & u h d g 0 % b & 7 5 / b ' \ q 5 ) u h d g 0 % b & 7 5 / b ' \ q ) 7 0 g l v d e o h g 0 % b & 7 5 / b ' \ q k 1 r d f f h v v ) 7 0 h q d e o h g 0 d l o e r [ h p s w \ 0 % b & 7 5 / b ' \ q k 5 : d f f h v v ) 7 0 h q d e o h g 5 ) 0 h v v d j h 0 % b & 7 5 / b ' \ q k 5 h d g d f f h v v ) 7 0 h q d e o h g 0 d l o e r [ i u h h 0 % b & 7 5 / b ' \ q k 5 : d f f h v v ) 7 0 h q d e o h g , & 0 h v v d j h 0 % b & 7 5 / b ' \ q k 5 h d g d f f h v v 0 % b ( 1 k r u 9 & & 2 ) ) ) 7 0 h q d e o h g 0 d l o e r [ i u h h 0 % b & 7 5 / b ' \ q k 5 : d f f h v v 0 % b ( 1 k r u 9 & & 2 ) ) 0 % b ( 1 k r u 9 & & 2 ) ) 9 & & 2 1 d q g 0 % b ( 1 k , & z u l w h p v j 5 ) z u l w h p v j , & u h d g p v j 5 ) u h d g p v j : d w f k g r j w u l j 0 d l o e r [ i u h h 0 6 y 9 st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 44/220 docid027603 rev 4 5.2 gpo gpo signal is used to alert the i 2 c host of external rf events or st25dvxxx processes activity. several causes could be used to r equest a host interruption. rf user can also directly drive gpo pin level using a dedicated rf command. 5.2.1 st25dvxxx interrupt capabilities on rf events st25dvxxx supports multi interruption mode and can report several events occurring through rf interface. in this chapter, all drawings are referrin g to the open drain version of gpo output (st25dvxxk-ie). the reader can retrieve the behavior of cmos version (st25dvxxk-jf) by inverting the gpo curve polarity and replace in text ?released? or ?high-z? by ?pull to ground?. supported rf events is listed hereafter: docid027603 rev 4 45/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 rf_user: ? gpo output level is controlled by manage gpo command (set or reset) ? when rf_user is activated, gpo level is changed after eof of st25dv response to a manage gpo set or reset command (see section 7.6.30: manage gpo ). ? rf_user is prevalent over all other gpo events when set by manage gpo command (other interrupts are still visible in it_sts_dyn stat us register, but do not change gpo output level). figure 12. rf_user chronogram 0 6 y 9 9 & ' v h q g v d 0 d q d j h * 3 2 f r p p d q g z l w k y d o x h k u h v h w * 3 2 d q g 6 7 ' 9 u h s o l h v * 3 2 5 ) b 8 6 ( 5 l v v h w k l j k = o r z d i w h u 6 7 ' 9 u h v s r q v h 6 2 ) ( 2 ) 9 & ' v h q g v d 0 d q d j h * 3 2 f r p p d q g d q \ y d o x h d q g 6 7 ' 9 v w d \ v t x l h w f r p p d q g q r w i r u w k l v 9 , & & r u t x l h w v w d w h * 3 2 5 ) b 8 6 ( 5 u h p d l q v k l j k = 0 d q d j h * 3 2 f r p p d q g * 3 2 5 ) b 8 6 ( 5 2 ' * 3 2 5 ) b 8 6 ( 5 2 ' 6 2 ) 0 d q d j h * 3 2 k f r p p d q g ( 2 ) 9 & ' v h q g v d 0 d q d j h * 3 2 f r p p d q g z l w k y d o x h k v h w * 3 2 d q g 6 7 ' 9 u h s o l h v * 3 2 5 ) b 8 6 ( 5 l v w l h g o r z d i w h u 6 7 ' 9 u h v s r q v h w * 3 2 5 ) b 8 6 ( 5 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) 0 d q d j h * 3 2 k f r p p d q g ( 2 ) 9 & ' v h q g v d 0 d q d j h * 3 2 f r p p d q g d q \ y d o x h d q g 6 7 ' 9 u h s o l h v z l w k h u u r u * 3 2 5 ) b 8 6 ( 5 u h p d l q v k l j k = * 3 2 5 ) b 8 6 ( 5 2 ' 6 2 ) 0 d q d j h * 3 2 f r p p d q g ( 2 ) w 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ w 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 9 & ' v h q g v d q \ f r p p d q g r w k h u w k d q 0 d q d j h * 3 2 f r p p d q g d q g 6 7 ' 9 u h s o l h v * 3 2 5 ) b 8 6 ( 5 u h p d l q v k l j k = * 3 2 5 ) b 8 6 ( 5 2 ' 6 2 ) $ q \ r w k h u f r p p d q g ( 2 ) w : w 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 46/220 docid027603 rev 4 rf_activity : ? gpo output level reflects the rf activity. ? when rf_activity is activated, a gpo output level change from rf command eof to st25dv response eof. figure 13. rf_activity chronogram 0 6 y 9 9 & ' v h q g v d z u l w h f r p p d q g d q g 6 7 ' 9 u h s o l h v d i w h u z u l w h f r p s o h w h g * 3 2 5 ) b $ & 7 , 9 , 7 < l v u h o h d v h g d i w h u 6 7 ' 9 u h v s r q v h 6 2 ) ( 2 ) 9 & ' v h q g v d f r p p d q g d q g 6 7 ' 9 v w d \ v t x l h w 6 w d \ 4 x l h w f r p p d q g f r p p d q g q r w i r u w k l v 9 , & & r u t x l h w v w d w h * 3 2 5 ) b $ & 7 , 9 , 7 < u h p d l q v k l j k = p : w 9 & ' & r p p d q g * 3 2 5 ) b $ & 7 , 9 , 7 < 2 ' * 3 2 5 ) b $ & 7 , 9 , 7 < 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) : u l w h f r p p d q g ( 2 ) 9 & ' v h q g v d f r p p d q g d q g 6 7 ' 9 u h s o l h v * 3 2 5 ) b $ & 7 , 9 , 7 < l v u h o h d v h g d i w h u 6 7 ' 9 u h v s r q v h w * 3 2 5 ) b $ & 7 , 9 , 7 < 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) 9 & ' f r p p d q g ( 2 ) 9 & ' v h q g v d z u l w h f r p p d q g z l w k r s w l r q i o d j v h w w r d q g 6 7 ' 9 u h s o l h v d i w h u u h f h l y l q j ( 2 ) * 3 2 5 ) b $ & 7 , 9 , 7 < l v u h o h d v h g d i w h u 6 7 ' 9 u h v s r q v h ! p : w * 3 2 5 ) b $ & 7 , 9 , 7 < 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) : u l w h f r p p d q g ( 2 ) ( 2 ) w 9 & ' v h q g v d q , q y h q w r u \ v o r w v f r p p d q g d q g 6 7 ' 9 u h s o l h v l q l w v v o r w * 3 2 5 ) b $ & 7 , 9 , 7 < l v u h o h d v h g d i w h u 6 7 ' 9 u h v s r q v h * 3 2 5 ) b $ & 7 , 9 , 7 < 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) , q y h q w r u \ f r p p d q g ( 2 ) ( 2 ) w ( 2 ) 6 o r w 6 o r w q docid027603 rev 4 47/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 rf_interrupt: ? a pulse is emitted on gpo by manage gpo command (interrupt). ? when rf_interrupt is activated, a pulse of duration it_time is emitted after eof of st25dv response to a manage gpo interrupt command (see section 7.6.30: manage gpo ). figure 14. rf_interrupt chronogram field_change: ? a pulse is emitted on gpo to sig nal a change in rf field state. ? when field_change is activated, and when rf field appear or disappear, gpo emits a pulse of duration it_time. ? in case of rf field disappear, the pulse is emitted only if v cc power supply is present. ? if rf is configured in rf_sleep mode, fi eld change are not re ported on gpo, even if field_change event is activated, as shown in table 15 . 0 6 y 9 6 2 ) ( 2 ) 9 & ' v h q g v d 0 d q d j h * 3 2 f r p p d q g d q \ y d o x h d q g 6 7 ' 9 v w d \ v t x l h w f r p p d q g q r w i r u w k l v 9 , & & r u t x l h w v w d w h * 3 2 5 ) b , 1 7 ( 5 5 8 3 7 u h p d l q v k l j k = 0 d q d j h * 3 2 f r p p d q g * 3 2 5 ) b , 1 7 ( 5 5 8 3 7 2 ' 9 & ' v h q g v d 0 d q d j h * 3 2 f r p p d q g z l w k y d o x h k * 3 2 h p l w s x o v h d q g 6 7 ' 9 u h s o l h v * 3 2 5 ) b , 1 7 ( 5 5 8 3 7 j h q h u d w h v d s x o v h r i g x u d w l r q , 7 b 7 , 0 ( d i w h u 6 7 ' 9 u h v s r q v h w * 3 2 5 ) b , 1 7 ( 5 5 8 3 7 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) 0 d q d j h * 3 2 k f r p p d q g ( 2 ) 9 & ' v h q g v d 0 d q d j h * 3 2 f r p p d q g d q \ y d o x h d q g 6 7 ' 9 u h s o l h v z l w k h u u r u * 3 2 5 ) b , 1 7 ( 5 5 8 3 7 u h p d l q v k l j k = * 3 2 5 ) b , 1 7 ( 5 5 8 3 7 2 ' 6 2 ) 0 d q d j h * 3 2 f r p p d q g ( 2 ) w 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 9 & ' v h q g v d q \ f r p p d q g r w k h u w k d q 0 d q d j h * 3 2 f r p p d q g d q g 6 7 ' 9 u h s o l h v * 3 2 5 ) b , 1 7 ( 5 5 8 3 7 u h p d l q v k l j k = * 3 2 5 ) b , 1 7 ( 5 5 8 3 7 2 ' 6 2 ) $ q \ r w k h u f r p p d q g ( 2 ) w : w 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 48/220 docid027603 rev 4 figure 15. field_ change chronogram rf_put_msg: ? a pulse is emitted on gpo when a message is successfully written by rf in fast transfer mode mailbox. ? when rf_put_msg is activated, a pulse of duration it_time is emitted on gpo at completion of valid write message or fast write message commands (after eof of st25dv response). table 15. field_change when rf is disabled or in sleep mode rf_disable rf_sleep gpo behavior when field_detect is enabled 00 a pulse is emitted on gpo if rf field appears or disappears (1) 1. assuming that gpo output is enabled (gpo_en = 1). 10 x1 gpo remains high-z (od) or tied low (cmos) it_sts_dyn register is not updated. x1 0 6 y 9 5 ) i l h o g g l v d s s h d u v d q g 6 7 ' 9 l v s r z h u h g w k u r x j k 9 & & * 3 2 ) , ( / ' b & + $ 1 * ( j h q h u d w h v d s x o v h g x u l q j , 7 b 7 , 0 ( * 3 2 ) , ( / ' b & + $ 1 * ( 2 ' 5 ) i l h o g d s s h d u v * 3 2 ) , ( / ' b & + $ 1 * ( j h q h u d w h v d s x o v h g x u l q j , 7 b 7 , 0 ( w * 3 2 ) , ( / ' b & + $ 1 * ( 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) ) l u v w 9 & ' f r p p d q g ( 2 ) 5 ) i l h o g g l v d s s h d u v d q g 6 7 ' 9 l v q r w s r z h u h g w k u r x j k 9 & & * 3 2 ) , ( / ' b & + $ 1 * ( g r h v q ? w j h q h u d w h v d q \ s x o v h 5 ) i l h o g 5 ) i l h o g w 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) 9 & ' f r p p d q g ( 2 ) * 3 2 ) , ( / ' b & + $ 1 * ( 2 ' 5 ) i l h o g w 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) 9 & ' f r p p d q g ( 2 ) docid027603 rev 4 49/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 figure 16. rf_put_msg chronogram rf_get_msg: ? a pulse is emitted on gpo when rf has successfully read a message, up to its last byte, in fast transfer mode mailbox. ? when rf_get_msg is activated, a pulse of duration it_time is emitted on gpo at completion of valid read message or fast read message commands (after eof of st25dv response), and end of message has been reached. 0 6 y 9 9 & ' v h q g v d : u l w h 0 h v v d j h r u ) d v w : u l w h 0 h v v d j h f r p p d q g d q g 6 7 ' 9 u h s o l h v z l w k h u u r u * 3 2 5 ) b 3 8 7 b 0 6 * u h p d l q v k l j k = 6 2 ) ( 2 ) 9 & ' v h q g v : u l w h 0 h v v d j h r u ) d v w : u l w h 0 h v v d j h f r p p d q g d q g 6 7 ' 9 v w d \ v t x l h w f r p p d q g q r w i r u w k l v 9 , & & r u t x l h w v w d w h * 3 2 5 ) b 3 8 7 b 0 6 * v w d \ v k l j k = : u l w h 0 v j & r p p d q g * 3 2 5 ) b 3 8 7 b 0 6 * 2 ' * 3 2 5 ) b 3 8 7 b 0 6 * 2 ' 6 2 ) : u l w h 0 v j f r p p d q g ( 2 ) 9 & ' v h q g v d : u l w h 0 h v v d j h r u ) d v w : u l w h 0 h v v d j h f r p p d q g d q g 6 7 ' 9 u h s o l h v z l w k q r h u u r u * 3 2 5 ) b 3 8 7 b 0 6 * j h q h u d w h v d s x o v h g x u l q j , 7 b 7 , 0 ( d i w h u 6 7 ' 9 u h v s r q v h w * 3 2 5 ) b 3 8 7 b 0 6 * 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) : u l w h 0 v j f r p p d q g ( 2 ) w 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 9 & ' v h q g v d d q \ r w k h u f r p p d q g w k d q : u l w h 0 h v v d j h r u ) d v w : u l w h 0 h v v d j h f r p p d q g v d q g 6 7 ' 9 u h s o l h v * 3 2 5 ) b 3 8 7 b 0 6 * u h p d l q v k l j k = * 3 2 5 ) b 3 8 7 b 0 6 * 2 ' 6 2 ) $ q \ r w k h u f r p p d q g ( 2 ) w 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 50/220 docid027603 rev 4 figure 17. rf_get_msg chronogram 0 6 y 9 9 & ' v h q g v d 5 h d g 0 h v v d j h r u ) d v w 5 h d g 0 h v v d j h f r p p d q g d q g 6 7 ' 9 u h s o l h v z l w k h u u r u * 3 2 5 ) b * ( 7 b 0 6 * u h p d l q v k l j k = 6 2 ) ( 2 ) 9 & ' v h q g v 5 h d g 0 h v v d j h r u ) d v w 5 h d g 0 h v v d j h f r p p d q g d q g 6 7 ' 9 v w d \ v t x l h w f r p p d q g q r w i r u w k l v 9 , & & r u t x l h w v w d w h * 3 2 5 ) b * ( 7 b 0 6 * v w d \ v k l j k = 5 h d g 0 v j & r p p d q g * 3 2 5 ) b * ( 7 b 0 6 * 2 ' * 3 2 5 ) b * ( 7 b 0 6 * 2 ' 6 2 ) 5 h d g 0 v j f r p p d q g ( 2 ) 9 & ' v h q g v d 5 h d g 0 h v v d j h r u ) d v w 5 h d g 0 h v v d j h f r p p d q g d q g 6 7 ' 9 u h s o l h v z l w k q r h u u r u * 3 2 5 ) b * ( 7 b 0 6 * j h q h u d w h v d s x o v h g x u l q j , 7 b 7 , 0 ( d i w h u 6 7 ' 9 u h v s r q v h w * 3 2 5 ) b * ( 7 b 0 6 * 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) 5 h d g 0 v j f r p p d q g ( 2 ) w 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 9 & ' v h q g v d q \ r w k h u f r p p d q g w k d q 5 h d g 0 h v v d j h r u ) d v w 5 h d g 0 h v v d j h f r p p d q g v d q g 6 7 ' 9 u h s o l h v * 3 2 5 ) b * ( 7 b 0 6 * u h p d l q v k l j k = * 3 2 5 ) b * ( 7 b 0 6 * 2 ' 6 2 ) $ q \ r w k h u f r p p d q g ( 2 ) w 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ docid027603 rev 4 51/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 rf_write: ? when rf_write is activated, a pulse of du ration it_time is emitted at completion of a valid rf write operation in eeprom (after eof of st25dv response). ? following commands trigger the rf_write interrupt after a valid write operation in eeprom: ? write single block ? extended write single block ? write multiple block ? extended write multiple block ? lock block ? extended lock block ? write afi ? lock afi ? write dsfid ? lock dsfid ? write configuration ? write password ? note that writing in dynamic registers or fast transfer mode mailbox does not trigger rf_write interrupt (no wr ite operation in eeprom). st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 52/220 docid027603 rev 4 figure 18. rf_write chronogram 5.2.2 gpo and power supply when at the same time rf field is present and v cc is on, gpo is acting as configured in gpo, gpo_ctrl_dyn and it_time registers. when the rf field disappears, the gpo state is reset and the output level is set to high-z (open drain) or tied low (cmos). interruption status in it_sts_dyn register is maintained until next i 2 c read or v cc power off. 0 6 y 9 9 & ' v h q g v d z u l w h f r p p d q g d q g 6 7 ' 9 u h s o l h v d i w h u z u l w h f r p s o h w h g * 3 2 5 ) b : 5 , 7 ( j h q h u d w h v d s x o v h g x u l q j , 7 b 7 , 0 ( d i w h u 6 7 ' 9 u h v s r q v h 6 2 ) ( 2 ) 9 & ' v h q g v d q \ f r p p d q g d q g 6 7 ' 9 v w d \ v t x l h w f r p p d q g q r w i r u w k l v 9 , & & r u t x l h w v w d w h 5 ) b $ & 7 , 9 , 7 < u h p d l q v k l j k = p : w 9 & ' & r p p d q g * 3 2 5 ) b : 5 , 7 ( 2 ' * 3 2 5 ) b : 5 , 7 ( 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) : u l w h f r p p d q g ( 2 ) 9 & ' v h q g v d z u l w h f r p p d q g d q g 6 7 ' 9 u h s o l h v z l w k h u u r u * 3 2 5 ) b : 5 , 7 ( u h p d l q v k l j k = w * 3 2 5 ) b : 5 , 7 ( 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) : u l w h f r p p d q g ( 2 ) 9 & ' v h q g v d z u l w h f r p p d q g z l w k r s w l r q i o d j v h w w r d q g 6 7 ' 9 u h s o l h v d i w h u u h f h l y l q j ( 2 ) * 3 2 5 ) b : 5 , 7 ( j h q h u d w h v d s x o v h g x u l q j , 7 b 7 , 0 ( d i w h u 6 7 ' 9 u h v s r q v h ! p : w * 3 2 5 ) b : 5 , 7 ( 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) : u l w h f r p p d q g ( 2 ) ( 2 ) w 9 & ' v h q g v d q \ r w k h u f r p p d q g w k d q d z u l w h f r p p d q g * 3 2 5 ) b : 5 , 7 ( u h p d l q v k l j k = w * 3 2 5 ) b : 5 , 7 ( 2 ' 6 2 ) ( 2 ) 6 7 ' 9 u h s o \ 6 2 ) $ q \ r w k h u f r p p d q g ( 2 ) docid027603 rev 4 53/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 when v cc is not present, or st25dvxxx is in lo w power mode, all events are available on gpo pin, assuming pull-up resistor is supplie d with correct voltage (open drain-ie version) or v dcg is powered (cmos-jf version). host ca n be waken up using gpo interrupt in any power condition. exception is field_change when rf field is falling, which can?t be reported on gpo output if v cc is off (no power supply on st25dvxxx) 5.2.3 gpo registers four registers are dedicated to this feature: ? two static registers in system configuration ? two dynamic registers table 16. gpo interrupt capabilities in function of rf field rf field on rf field off gpo state is function of rf events (1) 1. if pull-up resistor is powered (open drain-ie version), and v dcg is powered (cmos ?jf version). gpo remains high-z (od) or tied low (cmos) table 17. gpo interrupt capa bilities in fu nction of v cc power supply gpo events v cc off v cc on and lpd high (1) (low power mode) 1. for stm25dvxxk-jf only. v cc on and lpd low (1) field_change if rf field disappears gpo remains high-z (od) or tied low (cmos) pulse emitted on gpo (2) 2. if pull-up resistor is powered (open drain-ie version) and v dcg is powered (cmos-jf version). pulse emitted on gpo any other activated rf event gpo state is function of rf events (2) gpo state is function of rf events (2) gpo state is function of rf events (2) st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 54/220 docid027603 rev 4 ? enables the interruption source, and enable gpo output. ? several interruption sources can be enabled simultaneously. ? the updated value is valid for the next co mmand (except for the rf_write interrupt, which is valid right after eo f of the write configuration command if enabled through rf). ? the gpo_en bit (b7) allows to disable gp o output (high-z for open drain version, driven low for cmos version). interruptions are still reported in it_sts_dyn register. ? rf configuration security session (present rf password 0) or i 2 c security session (present i 2 c password) must be open in order to write the gpo register. table 18. gpo (1) rf command read configuration (cmd code a0h) @00h write configuration (cmd code a1h) @00h type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2=1, 0000h type r always, w if i 2 c security session is open bit name function factory value b0 rf_user_en 0: disabled 1: gpo output level is controlled by manage gpo command (set/reset) 0b b1 rf_activity_en 0: disabled 1: gpo output level changes from rf command eof to response eof. 0b b2 rf_interrupt_en 0: disabled 1: gpo output level is controlled by manage gpo command (pulse). 0b b3 field_change_en 0: disabled 1: a pulse is emitted on gpo, when rf field appears or disappears. 1b b4 rf_put_msg_en 0: disabled 1: a pulse is emitted on gpo at completion of valid rf write message command. 0b b5 rf_get_msg_en 0: disabled 1: a pulse is emitted on gpo at completion of valid rf read message command if end of message has been reached. 0b b6 rf_write_en 0: disabled 1: a pulse is emitted on gpo at comple tion of valid rf write operation in eeprom. 0b b7 gpo_en 0: gpo output is disabled. gpo is high-z (open drain) or 0 (cmos) 1: gpo output is enabled. gpo outputs enabled interrupts. 1b 1. refer to table 8: system configuration memory map for the gpo register. docid027603 rev 4 55/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 ? defines interrupt pulse duration on gpo pin for the flowing events: rf_interrupt, field_change, rf_put_msg, rf_get_msg and rf_write. ? see it pulse duration equation: for interrupt duration calculation. ? rf configuration security session (present rf password 0) or i 2 c security session (present i 2 c password) must be open in order to write it_time register. table 19. it_time (1) rf command read configuration (cmd code a0h) @01h write configuration (cmd code a1h) @01h type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2=1, 0001h type r always, w if i 2 c security session is open bit name function factory value b2-b0 it_time pulse duration = 301 us - it_time x 37.65 us 2 us 011b b7-b3 rfu - 00000b 1. refer to table 8: system configuration memory map for the it_time register. table 20. gpo_ctrl_dyn (1) rf command read dynamic configuration (cmd code adh) @00h write dynamic configuration (cmd code aeh) @00h fast read dynamic configuration (cmd code cdh) @00h fast write dynamic configuration (cmd code ceh) @00h type ro i 2 c address e2 = 0, 2000h type b0-b6: ro - b7 : r always, w always bit name function factory value b0 rf_user_en 0: disabled 1: gpo output level is controlled by manage gpo command (set/reset) 0b b1 rf_activity_en 0: disabled 1: gpo output level changes from rf command sof to response eof. 0b b2 rf_interrupt_en 0: disabled 1: gpo output level is controlled by manage gpo command (pulse). 0b st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 56/220 docid027603 rev 4 ? allows i 2 c host to dynamically enable or disabl e gpo output by writing in gpo_en bit (b7). ? gpo_en bit of gpo_ctrl_dyn register is prevalent over gpo_en bit of gpo register. ? at power up, and each time gpo register is updated, gpo_ctrl_dyn content is copied from gpo register. ? gpo_ctrl_dyn is a volatile register. value is maintained only if at least one of the two power sources is present (rf field or v cc ). ? gpo_ctrl_dyn bit 7 (gpo_en) can be written even if i 2 c security session is closed (i 2 c password not presented) but is read only for rf user. ? modifying gpo_ctrl_dyn, the bit 7 gpo_en does not affect the value of gpo register bit 7 gpo_en b3 field_change_en 0: disabled 1: a pulse is emitted on gpo, when rf field appears or disappears. 1b b4 rf_put_msg_en 0: disabled 1: a pulse is emitted on gpo at completion of valid rf write message command. 0b b5 rf_get_msg_en 0: disabled 1: a pulse is emitted on gpo at completion of valid rf read message command if end of message has been reached. 0b b6 rf_write_en 0: disabled 1: a pulse is emitted on gpo at comple tion of valid rf write operation in eeprom. 0b b7 gpo_en 0: gpo output is disabled. gpo is high-z (open drain) or 0 (cmos) 1: gpo output is enabled. gpo outputs enabled interrupts. 1b 1. refer to table 9: dynamic registers memory map for the gpo_ctrl_dyn register. table 20. gpo_ctrl_dyn (1) (continued) rf command read dynamic configuration (cmd code adh) @00h write dynamic configuration (cmd code aeh) @00h fast read dynamic configuration (cmd code cdh) @00h fast write dynamic configuration (cmd code ceh) @00h type ro i 2 c address e2 = 0, 2000h type b0-b6: ro - b7 : r always, w always bit name function factory value docid027603 rev 4 57/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 ? cumulates all events which generate interruptions. it should be checked by i 2 c host to know which event triggered an interrupt on gpo pin. ? when enabled, rf events are reported in it _sts_dyn register even if gpo output is disabled though the gpo_en bit. ? once read the itsts_dyn register is cleared (set to 00h). ? at power up, it_sts_dyn content is cleared (set to 00h). ? it_sts_dyn is a volatile register. value is maintained only if at least one of the two power sources is present (rf field or v cc ). 5.2.4 configuring gpo gpo and interruption pulse duration can be configured by rf user or by i 2 c host. one or more interrupts can be enabled at same time. rf user can use read configuration and writ e configuration commands to set accordingly the gpo and it_time registers, after presenting a valid rf configuration password to open rf configuration security session. table 21. it_sts_dyn (1) rf command no access type i 2 c address e2 = 0, 2005h type ro bit name function factory value b0 rf_user 0: manage gpo reset gpo 1: manage gpo set gpo 0b b1 rf_activity 0: no rf access 1: rf access 0b b2 rf_interrupt 0: no manage gpo interrupt request 1: manage gpo interrupt request 0b b3 field_falling 0: no rf field falling 1: rf field falling 0b b4 field_rising 0: no rf field rising 1: rf field rising 0b b5 rf_put_msg 0: no message put by rf in ftm mailbox 1: message put by rf in ftm mailbox 0b b6 rf_get_msg 0: no message read by rf from ftm mailbox 1: message read by rf from ftm mailbox, and end of message has been reached. 0b b7 rf_write 0: no write in eeprom 1: write in eeprom 0b 1. refer to table 9: dynamic registers memory map for the it_sts_dyn register. st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 58/220 docid027603 rev 4 i 2 c host can write gpo and it_time registers, after presenting a valid i 2 c password to open i 2 c security session. enabling or disabling gpo output: ? rf user and i 2 c host can disable or enable gpo output at power up time by writing in gpo_en bit 7 of gpo register (if write access is granted). ? i 2 c host can temporarily enable or disabl e gpo output at any time by toggling gpo_en bit 7 of gpo_ctrl_dyn register. no password is requ ired to write into gpo_ctrl_dyn register. ? disabling gpo output by writin g in gpo_en bit (either in gpo or in gpo_ctrl_dyn registers) does not disable interruption report in it_sts_dyn status register. interruption pulse duration configuration: ? interrupt pulse duration is configured by writing pulse duration value in it_time register. ? pulse duration is calculat ed with the following equation it pulse duration equation: table 22. enabling or disabling gpo interruptions gpo bit 7: gpo_en gpo_ctrl_dyn bit 7: gpo_en gpo output 0 0 gpo remains high-z (od) or tied low (cmos) 1 0 gpo remains high-z (od) or tied low (cmos) 0 1 activated rf events are reported on gpo output (1) 1 1 activated rf events are reported on gpo output (1) 1. if pull-up resistor is powered (open drain -ie version), and v dcg is powered (cmos ?jf version). it pulse duration 301 s it_time 37.65 s2 s ? = docid027603 rev 4 59/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 5.3 energy ha rvesting (eh) 5.3.1 energy harvesting registers table 23. eh_mode (1) rf command read configuration (cmd code a0h) @02h write configuration (cmd code a1h) @02h type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2 = 1, 0002h type r always, w if i 2 c security session is open bit name function factory value b0 eh_mode 0: eh forced after boot 1: eh on demand only 1b b7-b1 rfu - 0000000b 1. refer to table 8: system configuration memory map for the eh_mode register. table 24. eh_ctrl_dyn (1) rf command read dynamic configuration (cmd code adh) @02h fast read dynamic configuration (cmd code cdh) @02h write dynamic configuration (cmd code aeh) @02h fast write dynamic configuration (cmd code ceh) @02h type b0: r always, w ? b1 - b7: ro i 2 c address e2 = 0, 2002h type b0: r always, w always b1-b7: ro bit name function factory value b0 eh_en 0: disable eh feature 1: enable eh feature 0b b1 en_on 0: eh feature is disabled 1: eh feature is enabled 0b b2 field_on 0: rf field is not detected 1: rf field is present and st 25dvxxx may communicate in rf depending of power source b3 vcc_on 0: no dc supply detected on v cc pin or low power down mode is forced (lpd is high) 1: v cc supply is present and low power down mode is not forced (lpd is low) depending of power source b7-b4 rfu - 0b st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 60/220 docid027603 rev 4 5.3.2 energy harvesti ng feature description the usage of energy harvesting element ca n be defined in configuration register eh_mode. when the energy harvesting mode is disabled or the rf fi eld strength is not sufficient, the energy harvesting analog voltage output v_eh is in high-z state. eh_mode static register is used to define th e energy harvesting default strategy after boot. at boot eh_en (in eh_ctrl_dy n register) is set depending eh_mode value as shown in table below: writing 0 in eh_mode at any time after boot will automatically set eh_e n bit to 1, and thus activate energy harvesting. writing 1 in eh_mode at any time after boot will not modify eh_en bit (until next reboot) and thus will not modify energ y harvesting current state. eh_ctrl_dyn allows to activate or deactiva te on the fly the energy harvesting (eh_en) and bring information on actual state of eh and state of power supplies : ? eh_on set reflects the eh_en bit value ? field_on is set in presence of a rf field ? vcc_on is set when host power supply is on, and low power-down mode is not forced. during boot, eh is not delivered to av oid alteration in device configuration. caution: communication is not guaranteed during eh delivery. refer to the application note an4913 (energy harvesting delivery impact on st25dvxxx behavior during rf communication). energy harvesting can be set even if st25dvxxx is in rf disabled or rf sleep mode, or in low power mode. in a ll these cases, st25dvxxx will deliver power on v_eh pin if rf field is present. energy harvesting voltage output is not regulated. 1. refer to table 9: dynamic registers memory map for the eh_ctrl_dyn register. table 25. energy harvesting at power-up eh_mode eh_en (at boot) energy harvesting at power-up 0 1 eh enabled after boot (when possible) 10 eh disabled initially, eh delivered on demand (when possible) docid027603 rev 4 61/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 5.3.3 eh delivery state diagram figure 19. eh delivery state diagram note: power is delivered on v_eh only if harvest ed energy is sufficient to supply st25dv and leave over power. grey color indicates the states wher e power is delivered on v_eh pin. 5 ) ) l h o g 2 ) ) 9 f f 2 ) ) 5 ) ) l h o g 2 ) ) 9 f f 2 1 9 f f 2 ) ) 9 f f 2 1 ( + b 0 2 ' ( 5 ) ) l h o g 2 1 9 f f 2 ) ) 5 ) ) l h o g 2 ) ) 5 ) ) l h o g 2 1 ( + b 0 2 ' ( 5 ) ) l h o g 2 1 9 f f 2 1 9 f f 2 ) ) 9 f f 2 1 5 ) ) l h o g 2 ) ) 5 ) ) l h o g 2 1 5 ) ) l h o g 2 1 9 f f 2 1 5 ) ) l h o g 2 ) ) 9 f f 2 1 5 ) ) l h o g 2 ) ) 5 ) ) l h o g 2 ) ) 5 ) ) l h o g 2 1 9 f f 2 ) ) 9 f f 2 1 9 f f 2 ) ) 5 ) ) l h o g 2 1 ( + b 0 2 ' ( 5 ) ) l h o g 2 ) ) 9 f f 2 1 ( + b 0 2 ' ( 9 f f 2 ) ) 5 ) : u l w h ( + b & 7 5 / b ' \ q r u 5 ) : u l w h ( + b 0 2 ' ( , & : u l w h ( + b & 7 5 / b ' \ q r u , & : u l w h ( + b 0 2 ' ( , & : u l w h ( + b & 7 5 / b ' \ q 5 ) : u l w h ( + b & 7 5 / b ' \ q : u l w h ( + b & 7 5 / b ' \ q : u l w h ( + b & 7 5 / b ' \ q r u : u l w h ( + b 0 2 ' ( 3 r z h u 2 ) ) ( + g h o l y h u h g ( + g h o l y h u h g 1 r ( + u h t x h v w h g 1 r ( + u h t x h v w h g 1 r ( + u h t x h v w h g ( + u h t x h v w h g q r w g h o l y h u h g 0 6 y 9 st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 62/220 docid027603 rev 4 5.3.4 eh delivery sequence figure 20. st25dvxxx energy harvesting delivery sequence 1. we suppose that the captured rf powe r is sufficient to trig eh delivery. 2. v_eh = 1 means some w are available on v_eh pin. v_eh = 0 means v_eh pin is in high-z. 5 ) ) l h o g % r r w 1 r % r r w 1 r % r r w % r r w : l w k ( + b 0 2 ' ( 9 f f ( + b ( 1 ( + b 2 1 9 b ( + 1 r % r r w : l w k ( + b 0 2 ' ( ( + b ( 1 ( + b 2 1 9 b ( + 5 h v h w ( + b ( 1 6 h w ( + b ( 1 5 h v h w ( + b ( 1 6 h w ( + b ( 1 5 h v h w ( + b ( 1 6 h w ( + b ( 1 6 h w ( + b ( 1 6 h w ( + b ( 1 6 h w ( + b ( 1 5 h v h w ( + b ( 1 5 h v h w ( + b ( 1 0 6 y 9 docid027603 rev 4 63/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 5.4 rf management feature 5.4.1 rf management registers 5.4.2 rf management feature description rf_mngt register is used to control the rf communication between st25dvxxx and a rf reader. table 26. rf_mngt (1) rf command read configuration (cmd code a0h) @03h write configuration (cmd code a1h) @03h type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2 = 1, 0003h type r always, w if i 2 c security session is open bit name function factory value b0 rf_disable 0: rf commands executed 1: rf commands not executed (error 0fh returned) 0b b1 rf_sleep 0: rf communication enabled 1: rf communication disabled (st25dv remains silent) 0b b7-b2 rfu - 000000b 1. refer to table 8: system configuration memory map for the rf_mngt register. table 27. rf_mngt_dyn (1) rf command no access type i 2 c address e2 = 0, 2003h type r always, w always bit name function factory value b0 rf_disable 0: rf commands executed 1: rf commands not executed (error 0fh returned) 0b b1 rf_sleep 0: rf communication enabled 1: rf communication disabled (st25dv remains silent) 0b b7-b2 rfu - 0000000b 1. refer to table 9: dynamic registers memory map for the rf_mngt register. st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 64/220 docid027603 rev 4 at boot time, and each time rf_mngt register it is updated, content of rf_mngt_dyn register is copied from rf_mngt register. the content of rf_mngt_dyn register is used during application to set st25dvxxx behavior. content of this dynamic register rf_mngt_dyn can be updated on the fly, to temporarily modify the behavior of st25dvxxx without affe cting the static value of rf_mngt which will be recovered at next por. rf_mngt register is composed of two bits (see table 27: rf_mngt_dyn ): rf_disable and rf_sleep for a normal usage of rf in terface, bits rf_sleep and rf _disable must be set to 0. for rf are offered three modes: ? rf sleep mode: ? when rf_sleep is set to 1, all rf co mmunications are disabled, rf interface doesn?t interpret commands, but minimi zes consumption of rf interface. ? rf disable mode: ? when rf_sleep is set to 0 and rf_disable is set to 1, rf commands are interpreted but not executed. in case of a valid co mmand, st25dv will respond after t1 with the error code 0fh. inventory and stay quiet commands are not answered. ? rf normal mode: ? in normal usage, rf_sleep and rf _disable are set to 0, st25dvxxx will process the request and respond accordingly when i 2 c is not accessing st25dvxxx. if i 2 c is busy, st25dv will respond to rf request with the error code 0fh. whatever rf_mngt register value, the field det ection remains available leaving to master the possibility to temporar ily open rf communication by overwriting value in rf_mngt_dyn dynamic register. docid027603 rev 4 65/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 5.5 interface arbitration st25dvxxx automatically arbitrates the exclusive usage of rf and i 2 c interfaces. arbitration scheme obeys to ?first talk first served? basic law. (see figure 21 ). figure 21. st25dvxxx, arbitration between rf and i 2 c rf transaction is terminated: ? at response eof if answer. ? at request eof is no answer. ? at rf field off. 3 r z h u 2 ) ) % r r w 5 ) p x w h , & p x w h 5 ) e x v \ , & f r p p d p g v d u h 1 r $ f n 6 7 ' 9 v w d q g e \ 5 ) i u h h , & i u h h , & e x v \ ) k r u q r u h v s r q v h w r 5 ) u h t x h v w v 9 & & 2 1 r u 5 ) i l h o g 2 1 % r r w g r q h , & v w d u w , & w u d q v l w l r q w h u p l q d w h g 5 ) u h t x h v w 6 2 ) 5 ) w u d q v d f w l r q w h u p l q d w h g 0 6 y 9 st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 66/220 docid027603 rev 4 i2c transaction is terminated: ? at the end of eeprom programming time afte r the stop condition of a successful write into eeprom (user memory or system configuration). se e section 6.4: i2c write operations for write time calculation. ? at stop condition for an y other i2c transaction ? at vcc power off ? at any i2c error (terminated before stop condition) ? at i2c timeout if it occurs when rf is busy, i 2 c interface answers by noack on any i 2 c command. when i 2 c is busy, rf commands receive no respon se (inventory, stay quiet, addressed commands) or error code 0fh for any other command. 5.6 data protection st25dvxxx provides a special data protection mechanism based on passwords that unlock security sessions. user memory can be protected for read and/or write access and system configuration can be protected from write access, both from rf and i 2 c assess. 5.6.1 data protection registers table 28. rfa1ss (1) rf command read configuration (cmd code a0h) @04h write configuration (cmd code a1h) @04h type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2 = 1, 0004h type r always, w if i 2 c security session is open bit name function factory value b1-b0 pwd_ctrl_a1 00: area 1 rf user security session can?t be open by password 01: area 1 rf user security session is open by rf_pwd_1 10: area 1 rf user security session is open by rf_pwd_2 11: area 1 rf user security session is open by rf_pwd_3 00b b3-b2 rw_protection_a1 00: area 1 rf access: read always allowed / write always allowed 01: area 1 rf access: read always allowed, write allowed if rf user security session is open 10: area 1 rf access: read always allowed, write allowed if rf user security session is open 11: area 1 rf access: read always allowed, write always forbidden 00b b7-b4 rfu - 0000b 1. refer to table 8: system configuration memory map for the rfa1ss register. docid027603 rev 4 67/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 table 29. rfa2ss (1) rf command read configuration (cmd code a0h) @06h write configuration (cmd code a1h) @06h type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2 = 1, 0006h type r always, w if i 2 c security session is open bit name function factory value b1-b0 pwd_ctrl_a2 00: area 2 rf user security session can?t be open by password 01: area 2 rf user security session is open by rf_pwd_1 10: area 2 rf user security session is open by rf_pwd_2 11: area 2 rf user security session is open by rf_pwd_3 00b b3-b2 rw_protection_a2 00: area 2 rf access: read always allowed, write always allowed 01: area 2 rf access: read always allowed, write allowed if rf user security session is open 10: area 2 rf access: read allowed if rf user security session is open, write allowed if rf user security session is open 11: area 2 rf access: read allowed if rf user security session is open, write always forbidden 00b b7-b4 rfu - 0000b 1. refer to table 8: system configuration memory map for the rfa2ss register. st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 68/220 docid027603 rev 4 table 30. rfa3ss (1) rf command read configuration (cmd code a0h) @08h write configuration (cmd code a1h) @08h type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2 = 1, 0008h type r always, w if i 2 c security session is open bit name function factory value b1-b0 pwd_ctrl_a3 00: area 3 rf user security session can?t be open by password 01: area 3 rf user security session is open by rf_pwd_1 10: area 3 rf user security session is open by rf_pwd_2 11: area 3 rf user security session is open by rf_pwd_3 00b b3-b2 rw_protection_a3 00: area 3 rf access: read always allowed / write always allowed 01: area 3 rf access: read always allowed, write allowed if rf user security session is open 10: area 3 rf access: read allowed if rf user security session is open, write allowed if rf user security session is open 11: area 3 rf access: read allowed if rf user security session is open, write always forbidden 00b b7-b4 rfu - 0000b 1. refer to table 8: system configuration memory map for the rfa3ss register. docid027603 rev 4 69/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 table 31. rfa4ss (1) rf command read configuration (cmd code a0h) @0ah write configuration (cmd code a1h) @0ah type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2 = 1, 000ah type r always, w if i 2 c security session is open bit name function factory value b1-b0 pwd_ctrl_a4 00: area 4rf user security session can?t be open by password 01: area 4 rf user security session is open by rf_pwd_1 10: area 4 rf user security session is open by rf_pwd_2 11: area 4 rf user security session is open by rf_pwd_3 00b b3-b2 rw_protection_a4 00: area 4 rf access: read always allowed, write always allowed 01: area 4 rf access: read always allowed, write allowed if rf user security session is open 10: area 4 rf access: read allowed if rf user security session is open, write allowed if rf user security session is open 11: area 4 rf access: read allowed if rf user security session is open, write always forbidden 00b b7-b4 rfu - 0000b 1. refer to table 8: system configuration memory map for the rfa4ss register. st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 70/220 docid027603 rev 4 table 32. i2css (1) rf command no access type i 2 c address e2 = 1, 000bh type r always, w if i 2 c security session is open bit name function factory value b1-b0 rw_protection_a1 00: area 1 i 2 c access: read always allowed, write always allowed 01: area 1 i 2 c access: read always allowed, write allowed if i 2 c user security session is open 10: area 1 i 2 c access: read always allowed, write always allowed 11: area 1 i 2 c access: read always allowed, write allowed if i 2 c user security session is open 00b b3-b2 rw_protection_a2 00: area 2 i 2 c access: read always allowed, write always allowed 01: area 2 i 2 c access: read always allowed, write allowed if i 2 c user security session is open 10: area 2 i 2 c access: read allowed if i 2 c user security session is open, write always allowed 11: area 2 i 2 c access: read allowed if i 2 c security session is open, write allowed if i 2 c security session is open 00b b5-b4 rw_protection_a3 00: area 3 i 2 c access: read always allowed, write always allowed 01: area 3 i 2 c access: read always allowed, write allowed if i 2 c user security session is open 10: area 3 i 2 c access: read allowed if i 2 c user security session is open, write always allowed 11: area 3 i 2 c access: read allowed if i 2 c security session is open, write allowed if i 2 c security session is open 00b b7-b6 rw_protection_a4 00: area 4 i 2 c access: read always allowed, write always allowed 01: area 4 i 2 c access: read always allowed, write allowed if i 2 c user security session is open 10: area 4 i 2 c access: read allowed if i 2 c user security session is open, write always allowed 11: area 4 i 2 c access: read allowed if i 2 c security session is open, write allowed if i 2 c security session is open 00b 1. refer to table 8: system configuration memory map for the i2css register. docid027603 rev 4 71/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 table 33. lock_ccfile (1) rf command lock block (cmd code 22h) @00h/01h ext lock block (cmd code 32h) @00h/01h read block (2) (cmd code 20h) @00h/01h fast read block (2) (cmd code c0h) @00h/01h ext read block (2) (cmd code 30h) @00h/01h fast ext read block (2) (cmd code c4h) @00h/01h read multi block (2) (cmd code 23h) @00h/01h ext read multi block (2) (cmd code 33h) @00h/01h fast read multi block (2) (cmd code c3h) @00h/01h fast ext read multi block (2) (cmd code c5h) @00h/01h get multi block ss (cmd code 2ch) @00h/01h ext get multi block ss (c md code 3ch) @00h/01h type r always b0: w if block 00h is not already locked, b1: w if block 01h is not already locked. i 2 c address e2 = 1, 000ch type r always, w if i 2 c security session is open bit name function factory value b0 lckbck0 0: block @ 00h is not write locked 1: block @ 00h is write locked 0b b1 lckbck1 0: block @ 01h is not write locked 1: block @ 01h is write locked 0b b7-b2 rfu - 000000b 1. refer to table 8: system configuration memory map for the lock_ccfile register. 2. with option flag set to 1. st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 72/220 docid027603 rev 4 table 34. lock_cfg (1) rf command read configuration (cmd code a0h) @0fh write configuration (cmd code a1h) @0fh type r always, w if rf configuration security session is open and configuration not locked i 2 c address e2 = 1, 000fh type r always, w if i 2 c security session is open bit name function factory value b0 lck_cfg 0: configuration is unlocked 1: configuration is locked 0b b7-b1 rfu - 0000000b 1. refer to table 8: system configuration memory map for the lock_cfg register. table 35. i2c_pwd (1) rf command no access type i 2 c address e2 = 1, 0900h to 0907h, present/write password command format. type r if i 2 c security session is open, w if i 2 c security session is open i 2 c address bit name function factory value 0900h b7-b0 i2c_pwd byte 7 (msb) of password for i 2 c security session 00h 0901h b7-b0 byte 6 of password for i 2 c security session 00h 0902h b7-b0 byte 5 of password for i 2 c security session 00h 0903h b7-b0 byte 4 of password for i 2 c security session 00h 0904h b7-b0 byte 3 of password for i 2 c security session 00h 0905h b7-b0 byte 2 of password for i 2 c security session 00h 0906h b7-b0 byte 1 of password for i 2 c security session 00h 0907h b7-b0 byte 0 (lsb) of password for i 2 c security session 00h 1. refer to table 8: system configuration memory map for the i2c_pwd register. docid027603 rev 4 73/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 table 36. rf_pwd_0 (1) rf command present password (cmd code b3h) write password (cmd code b1h) type wo if rf configuration security session is open i 2 c address no access type bit name function factory value b7-b0 rf_pwd_0 byte 0 (lsb) of password for rf configuration security session 00h b7-b0 byte 1 of password for rf configuration security session 00h b7-b0 byte 2 of password for rf configuration security session 00h b7-b0 byte 3 of password for rf configuration security session 00h b7-b0 byte 4 of password for rf configuration security session 00h b7-b0 byte 5 of password for rf configuration security session 00h b7-b0 byte 6 of password for rf configuration security session 00h b7-b0 byte 7 (msb) of password for rf configuration security session 00h 1. refer to table 8: system configuration memory map for the rf_pwd_0 register. table 37. rf_pwd_1 (1) rf command present password (cmd code b3h) write password (cmd code b1h) type wo if rf configuration security session is open with rf password 1 i 2 c address no access type bit name function factory value b7-b0 rf_pwd_1 byte 0 (lsb) of password 1 for rf user security session 00h b7-b0 byte 1 of password 1 for rf user security session 00h b7-b0 byte 2 of password 1 for rf user security session 00h b7-b0 byte 3 of password 1 for rf user security session 00h b7-b0 byte 4 of password 1 for rf user security session 00h b7-b0 byte 5 of password 1 for rf user security session 00h b7-b0 byte 6 of password 1 for rf user security session 00h b7-b0 byte 7 (msb) of password 1 for rf user security session 00h 1. refer to table 8: system configuration memory map for the rf_pwd_1 register. st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 74/220 docid027603 rev 4 table 38. rf_pwd_2 (1) rf command present password (cmd code b3h) write password (cmd code b1h) type wo if rf user security session is open with rf password 2 i 2 c address no access type bit name function factory value b7-b0 rf_pwd_2 byte 0 (lsb) of password 2 for rf user security session 00h b7-b0 byte 1 of password 2 for rf user security session 00h b7-b0 byte 2 of password 2 for rf user security session 00h b7-b0 byte 3 of password 2 for rf user security session 00h b7-b0 byte 4 of password 2 for rf user security session 00h b7-b0 byte 5 of password 2 for rf user security session 00h b7-b0 byte 6 of password 2 for rf user security session 00h b7-b0 byte 7 (msb) of password 2 for rf user security session 00h 1. refer to table 8: system configuration memory map for the rf_pwd_2 register. table 39. rf_pwd_3 (1) rf command present password (cmd code b3h) write password (cmd code b1h) type wo if rf user security session is open with rf password 3 i 2 c address no access type bit name function factory value b7-b0 rf_pwd_3 byte 0 (lsb) of password 3for rf user security session 00h b7-b0 byte 1 of password 3 for rf user security session 00h b7-b0 byte 2 of password 3 for rf user security session 00h b7-b0 byte 3 of password 3 for rf user security session 00h b7-b0 byte 4 of password 3 for rf user security session 00h b7-b0 byte 5 of password 3 for rf user security session 00h b7-b0 byte 6 of password 3 for rf user security session 00h b7-b0 byte 7 (msb) of password 3 for rf user security session 00h 1. refer to table 8: system configuration memory map for the rf_pwd_3 register. docid027603 rev 4 75/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 5.6.2 passwords and security sessions st25dvxxx provides protection of user memory and system conf iguration static registers. rf user and i 2 c host can access those protected data by opening security sessions with the help of passwords. access rights is more restricted when security sessions are closed, and less restricted when security sessions are open. dynamic registers and fast transfer mode mail box are not protected by any security session. there is three type of security sessions, as shown in table 41 : all passwords are 64-bits long, and default factory passwords value is 0000000000000000h. the st25dvxxx passwords management is organized around rf and i 2 c dedicated set of commands to access the dedicated registers in system configuration area where password values are stored. table 40. i2c_sso_dyn (1) rf command no access type i 2 c address e2 = 0, 2004h type ro bit name function factory value b0 i2c_sso 0: i 2 c security session close 1: i 2 c security session open (set or reset via i 2 c present password command) 0b b7-b1 rfu - 0b 1. refer to table 9: dynamic registers memory map for the i2c_ss0_dyn register. table 41. security session type security session open by presenting right granted when security session is open, and until it is closed rf user rf password 1, 2 or 3 (1) (rf_pwd_1, rf_pwd_2, rf_pwd_3) rf user access to protected user memory as defined in rfa i ss registers rf user write access to rf password 1, 2 or 3 (2) rf configuration rf password 0 (rf_pwd_0) rf user write access to conf iguration static registers rf user write access to rf password 0 i 2 c i 2 c password (i2c_pwd) i 2 c host access to protected user memory as defined in i2css register i 2 c host write access to configuration static registers i 2 c host write access to i 2 c password 1. password number must be the same as the one selected for protection. 2. write access to the password number corres ponding to the password number presented. st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 76/220 docid027603 rev 4 the dedicated password commands in rf mode are: ? write password command (code b1h): see section 7.6.35: write password . ? present password command (code b3h): see section 7.6.36: present password . rf user possible actions for security sessions are: ? open rf user security session : present password command, with password number 1, 2 or 3 and the valid corresponding password ? write rf password : present password command, with password number (0, 1, 2 or 3) and the current valid corresponding password. then write password command, with same password number (0, 1, 2 or 3) and the new corresponding password. ? close rf user security session : present password command, with a different password number than the one used to open session or any wrong password. or remove tag from rf field (por). ? open rf configuration security session : present password command, with password number 0 and the valid password 0. ? close rf configuration security session : present password command, with a password number different than 0, or password number 0 and wrong password 0. or remove tag from rf field (por). opening any new rf security session (user or configuration) automatically close the previously open one (even if it fails). there is no interaction between i 2 c and rf security sessions. both are independent, and can run in parallel. caution: if st25dvxxx is powered through v cc , removing v cc or setting lpd high during a rf command can abort the command. as a consequence, before writing a new password, rf user should check if v cc is on, by reading eh_ctrl_dyn register bit 3 (vcc_on), and eventually ask host to main tain or to shut down v cc , and not change voltage applied on lpd while issuing the write pa ssword command in order to avoid password corruption. docid027603 rev 4 77/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 figure 22. rf security sessions management the dedicated password commands in i 2 c mode are: ? i 2 c write password command: see section 6.6.2: i 2 c write password command description . ? i 2 c present password command: see section 6.6.2: i 2 c write password command description . i 2 c host possible actions for security sessions are: ? open i 2 c security session : i 2 c present password command with valid i 2 c password. ? write i 2 c password : i 2 c present password command with valid i 2 c password. then i 2 c write password command with new i 2 c password. ? close i 2 c security session : i 2 c present password command with wrong i 2 c password. or remove tag v cc power supply (por). ? check if i 2 c security session is open : i 2 c host can read the current status (open or closed) of i 2 c security session by reading the i2c_sso_dyn register. 5 ) i l h o g 2 ) ) 5 ) i l h o g 2 1 6 7 ' 9 r x w r i 5 ) i l h o g $ o o 5 ) v h f x u l w \ v h v v l r q v f o r v h g 5 ) v h f x u l w \ v h v v l r q [ r s h q h g \ f o r v h g $ q \ r w k h u f r p p d q g 3 u h v h q w 5 ) b 3 : ' b [ 2 . 5 ) v h f x u l w \ v h v v l r q \ r s h q h g [ f o r v h g 3 u h v h q w 5 ) b 3 : ' b \ 2 . 3 u h v h q w 5 ) b 3 : ' b [ 2 . 3 u h v h q w d q \ 5 ) s d v v z r u g q r w 2 . $ q \ r w k h u f r p p d q g $ q \ r w k h u f r p p d q g 0 6 y 9 st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 78/220 docid027603 rev 4 there is no interaction between i 2 c and rf security sessions. both are independent and can run in parallel. figure 23. i 2 c security sessions management 5.6.3 user memory protection on factory delivery, areas are not protected. each area can be individually protected in read and/or write access from rf and i 2 c. area 1 is always readable (from rf and i 2 c). furthermore, rf blocks 0 and 1 (i 2 c bytes 0000h to 00007h) can be independently write locked. user memory protection from rf access in rf mode, each memory area of the st25dvx xx can be individually protected by one out of three available passwords (rf password 1, 2 or 3), and each area can also have individual read/write access conditions. for each area, an rfa i ss register is used to: ? select the rf password that unlock the rf user security session for this area ? select the protection against read an d write operations for this area (see table 28: rfa1ss , table 29: rfa2ss , table 30: rfa3ss and table 31: rfa4ss for details about available read and write protections). 9 & & 2 ) ) 9 & & 2 1 9 & & 2 ) ) , & v h f x u l w \ v h v v l r q f o r v h g , & b 6 6 2 k , & v h f x u l w \ v h v v l r q r s h q h g , & b 6 6 2 k 3 u h v h q w , & b 3 : ' q r w 2 . $ q \ r w k h u f r p p d q g 3 u h v h q w , & b 3 : ' 2 . $ q \ r w k h u f r p p d q g 0 6 y 9 docid027603 rev 4 79/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 note: setting 00b in pwd_ctrl_a i field means that rf user secu rity session cannot be open by any password for the corresponding area. when updating rfa i ss registers, the new protection valu e is effective immediately after the register write completion. ? rf blocks 0 and 1 are exceptions to this protection mechanism: ? rf blocks 0 and 1 can be individually wr ite locked by issuing a (ext) lock single block rf command. once locked, they cannot be unlock through rf. lock_ccfile register is automatically updated when using (ext) lock single block command. ? a rf user needs no password to lock blocks 0 and/or 1. ? locking blocks 0 and/or 1 is possib le even if the configuration is locked (lock_cfg=1). ? locking blocks 0 and/or 1 is possib le even if the area is write locked. ? unlocking area1 (through rfa1ss register) does not unlock blocks 0 and 1 if they have been locked though (ext) lock block command. ? once locked, the rf user cannot unlock blocks 0 and/or 1 (can be done by i 2 c host). note: when areas size are modified (endai r egisters), rfaiss registers are not modified. user memory protection from i 2 c access in i 2 c mode, each area can also have individual read/write access conditions, but only one i 2 c password is used to unlock i 2 c security session for all areas. the i2css register is used to set protection against read and write operation for each area (see table 32: i2css for details about available read and write protections). when updating i2css registers, the new protec tion value is effective immediately after the register write completion. i 2 c user memory bytes 0000h to 0003h (rf block 0) and 0004h to 0007h (rf block 1) can be individually locked and unlocked by writi ng in the lock_ccfile register (by group of 4 bytes), independently of area 1 protection. un locking area 1 (through i2css register) does not unlock those bytes if they have been locked though the lock_ccfile register. note: when areas size are modified (endai r egisters), i2css register is not modified. retrieve the security status of a user memory block or byte rf user can read a block security status by issuing following rf commands: ? (ext) get multiple blocks security status command. ? (ext) (fast) read single block with option flag set to 1. ? (ext) (fast) read multiple blocks with option flag set to 1. st25dv will respond with a block security status containing a lock_bit flag as specified in iso 15693 standard. this lock_bit flag is set to one if block is locked against write. lock_bit flag value may vary if corresponding rf user security sessi on is open or closed. i 2 c host can retrieve a block security status by reading the i2css register to get security status of the corresponding area and by reading the i2c_sso_dyn register to know if i 2 c security session is open or closed . st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 80/220 docid027603 rev 4 for blocks 0 and 1 (bytes 0000h to 0007h in i 2 c user memory), lock status can also be read in the lock_ccfile register. 5.6.4 system memory protection by default, system memory (static registers) is write protected, both in rf and i 2 c. i 2 c host must open the i 2 c security session (by presenting a valid i 2 c password) to enable write access to system configuration static registers. i 2 c host doesn?t have read or write access to rf passwords. by default, i 2 c host can read all system configuratio n static registers (except rf passwords) in rf, to enable write access to system configur ation static registers, rf user must open the rf configuration security session (by pres enting a valid rf password 0) and system configuration must not be locked (lock_cfg=00h). rf doesn?t have read or write access to i 2 c password. by default, rf user can read all system configur ation static registers, except all passwords, lock_ccfile, lock_dsfid and lock_afi. rf configuration lock: ? rf write access to system configuration static registers can be locked by writing 01h in the lock_cfg register (by rf or i 2 c). ? rf user cannot unlock system configurati on if lock_cfg=01h, even after opening rf configuration security session (only i 2 c host can unlock system configuration). ? when system configuration is locked (lock_cfg=01h), it is still possible to change rf passwords (0 to 3). device identification registers: ? afi and dfsid registers can be independently locked by rf user, issuing respectively a lock afi and a lock dsfid command. lock is definitive: once locked, afi and dsfid registers cannot be unlocked (either by rf or i 2 c). system configuration locking mechanism (lock_cfg=01h) does not lock afi and dsfid registers. ? other device identification registers (mem_size, blk_si ze, ic_ref, uid, ic_rev) are read only registers for both rf and i 2 c. docid027603 rev 4 81/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 5.7 device parameter registers table 42. lock_dsfid (1) rf command lock dsfid (cmd code 2ah) type wo if dsfid not locked i 2 c address e2 = 1, 0010h type ro bit name function factory value b0 lock_dsfid 0: dsfid is not locked 1: dsfid is locked 0b b7-b1 rfu - 0000000b 1. refer to table 8: system configuration memory map for the lock_dsfid register. table 43. lock_afi (1) rf command lock afi (cmd code 28h) type wo if afi not locked i 2 c address e2 = 1, 0011h type ro bit name function factory value b0 lock_afi 0: afi is not locked 1: afi is locked 0b b7-b1 rfu - 0000000b 1. refer to table 8: system configuration memory map for the lock_afi register. st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 82/220 docid027603 rev 4 table 44. dsfid (1) rf command inventory (cmd code 01h) get system info (cmd code 2bh) ext get system info (cmd code 3bh) write dsfid (cmd code 28h) type r always, w if dsfid not locked i 2 c address e2 = 1, 0012h type ro bit name function factory value b7-b0 dsfid iso/iec 15693 data storage format identifier 00h 1. refer to table 8: system configuration memory map for the dsfid register. table 45. afi (1) rf command inventory (cmd code 01h) get system info (cmd code 2bh) ext get system info (cmd code 3bh) write afi (cmd code 27h) type r always, w if afi not locked i 2 c address e2 = 1, 0013h type ro bit name function factory value b7-b0 afi iso/iec 15693 applic ation family identifier 00h 1. refer to table 8: system configuration memory map for the afi register. docid027603 rev 4 83/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 table 46. mem_size (1) rf command get system info (2) (cmd code 2bh) ext get system info (cmd code 3bh) type ro i 2 c address e2=1, 0014h to 0015h type ro i 2 c address bit name function factory value 0014h b7-b0 mem_size address 0015h: lsb byte of the memory size expressed in rf blocks ST25DV04K-xx: 7fh st25dv16k-xx: ffh st25dv64k-xx: ffh 0015h b7-b0 address 0014h: msb byte of the memory size expressed in rf blocks ST25DV04K-xx: 00h st25dv16k-xx: 01h st25dv64k-xx: 07h 1. refer to table 8: system configuration memory map for the mem_size register. 2. only ST25DV04K-ie and ST25DV04K-jf table 47. blk_size (1) rf command get system info (2) (cmd code 2bh) ext get system info (cmd code 3bh) type ro i 2 c address e2 = 1, 0016h type ro bit name function factory value b7-b0 blk_size rf user memory block size 03h 1. refer to table 8: system configuration memory map for the blk_size register. 2. only ST25DV04K-ie and ST25DV04K-jf st25dvxxx specific features ST25DV04K st25dv16k st25dv64k 84/220 docid027603 rev 4 table 48. ic_ref (1) rf command get system info (cmd code 2bh) ext get system info (cmd code 3bh) type ro i 2 c address e2 = 1, 0017h type ro bit name function factory value b7-b0 ic_ref iso/iec 15693 ic reference ST25DV04K-ie: 24h st25dv16k-ie: 26h st25dv64k-ie: 26h ST25DV04K-jf: 24h st25dv16k-jf: 26h st25dv64k-jf: 26h 1. refer to table 8: system configuration memory map for the ic_ref register. table 49. uid (1) rf command inventory (cmd code 01h) get system info (cmd code 2bh) ext get system info (cmd code 3bh) type ro i 2 c address e2=1, 0018h to 001fh type ro i 2 c address bit name function factory value 0018h b7-b0 uid iso/iec 15693 uid byte 0 (lsb) ic manufacturer serial number 0019h b7-b0 iso/iec 15693 uid byte 1 001ah b7-b0 iso/iec 15693 uid byte 2 001bh b7-b0 iso/iec 15693 uid byte 3 001ch b7-b0 iso/iec 15693 uid byte 4 001dh b7-b0 iso/iec 15693 uid byte 5: st product code ST25DV04K-ie: 24h st25dv16k-ie: 26h st25dv64k-ie: 26h ST25DV04K-jf: 25h st25dv16k-jf: 27h st25dv64k-jf: 27h 001eh b7-b0 iso/iec 15693 uid byte 6: ic mfg code 02h 001fh b7-b0 iso/iec 15693 uid byte 7 (msb) e0h 1. refer to table 8: system configuration memory map for the uid register. docid027603 rev 4 85/220 ST25DV04K st25dv16k st25dv64k st25dvxxx specific features 219 table 50. ic_rev (1) 1. refer to table 8: system configuration memory map for the ic_rev register. rf command no access type i 2 c address e2 = 1, 0020h type ro bit name function factory value b7-b0 ic_rev ic revision depending on revision i 2 c operation ST25DV04K st25dv16k st25dv64k 86/220 docid027603 rev 4 6 i 2 c operation 6.1 i 2 c protocol the device supports the i 2 c protocol. this is summarized in figure 24: i 2 c bus protocol . any device that sends data to the bus is defin ed as a transmitter, and any device that reads data is defined as a receiver. the device that co ntrols the data transfer is known as the bus master, and the other as the slave device. a data transfer can only be initiated by the bus master, which also provides the serial clock for synchronization. the st25dvxxx device is a slave in all communications. figure 24. i 2 c bus protocol 6.1.1 start condition start is identified by a falling edge of serial data (sda) while the serial clock (scl) is stable in the high state. a start condition must precede any data transfer command. the device continuously monitors (except during a wr ite cycle) the sda and the scl for a start condition, and does not respond unless one is given. docid027603 rev 4 87/220 ST25DV04K st25dv16k st25dv64k i 2 c operation 219 6.1.2 stop condition stop is identified by a rising edge of serial data (sda) while the serial clock (scl) is stable and driven high. a stop condition terminates communication between the device and the bus master. a read command that is followed by noack can be followed by a stop condition to force the device into the standby mode. a st op condition at the end of a write command triggers the inte rnal write cycle. 6.1.3 acknowledge bit (ack) the acknowledge bit is used to indicate a succ essful byte transfer. the bus transmitter, whether a bus master or a slave device, releas es the serial data (sda) after sending eight bits of data. during the 9 th clock pulse period, the receiver pulls the sda low to acknowledge the receipt of the eight data bits. 6.1.4 data input during data input, the device samples serial da ta (sda) on the rising edge of the serial clock (scl). for correct device operation, the sda must be stable during the rising edge of the scl, and the sda signal must change only when the scl is driven low. 6.2 i 2 c timeout during the execution of an i2c operatio n, rf communications are not possible. to prevent rf communication freezing due to in advertent unterminated in structions sent to the i2c bus, the st25dvxxx features a timeout mechanism that automatically resets the i2c logic block. 6.2.1 i 2 c timeout on start condition i 2 c communication with the st25dvx xx starts with a valid star t condition, followed by a device select code. if the delay between the start condition and the following rising edge of the serial clock (scl) that samples the most significan t of the device select exceeds the t start_out time (see table 209: i 2 c ac characteristics up to 85c and table 210: i 2 c ac characteristics up to 125c ), the i2c logic block is reset and further incoming data transfer is ignored until the next valid start condition. i 2 c operation ST25DV04K st25dv16k st25dv64k 88/220 docid027603 rev 4 figure 25. i2c timeout on start condition 6.2.2 i 2 c timeout on clock period during data transfer on the i2c bus, if the serial clock pulse width high ( t chcl ) or serial clock pulse width low ( t clch ) exceeds the maximum value specified in table 209: i 2 c ac characteristics up to 85c and table 210: i 2 c ac characteristics up to 125c , the i2c logic block is reset and any further incoming data tr ansfer is ignored until the next valid start condition. 6.3 device addressing to start a communication between the bus ma ster and the slave device, the bus master must initiate a start condition. following this, the bus master sends the device select code, shown in table 51: device select code (on serial data (sda), the most significant bit first). the device select code consists of a 4-bit device type identifier and a 3-bit chip enable ?address? (e2,1,1). to address the memory array, the 4-bit device type identifier is 1010b. refer to table 51: device select code . the eighth bit is the read/ write bit (r w ). it is set to 1 for read and to 0 for write operations. if a match occurs on the device select code, the corresponding device gives an acknowledgment on serial data (sda) during the ninth bit time. if the device does not match the device select code, it de selects itself from the bus, and goes into standby mode. 0 6 9 6 & / 6 ' $ w 6 7 $ 5 7 b 2 8 7 6 w d u w f r q g l w l r q table 51. device select code device type identifier (1) 1. the most significant bi t, b7, is sent first. chip enable address rw b7 b6 b5 b4 b3 b2 b1 b0 device select code1010e2 (2) 2. e2 is not connected to any external pin. it is however used to address the st25dvxxx as described in section 4: memory management e2 = 0, access to user memory, dynamic registers or mailbox. e2 =1, access to system area. 11rw docid027603 rev 4 89/220 ST25DV04K st25dv16k st25dv64k i 2 c operation 219 6.4 i 2 c write operations following a start condition, the bus master sends a device select code with the read/ write bit (r w ) reset to 0. the device acknowledges this, and waits for two address bytes. the device responds to each address byte with an acknowledge bit, and then waits for the data byte. each data byte in the memory has a 16-bit (t wo-byte wide) address. the most significant byte (see table 53: address most significant byte ) is sent first, followed by the least significant byte (see table 54: address least significant byte ). bits b15 to b0 form the address of the byte in memory. when the bus master generates a stop conditio n immediately after the ack bit (in the tenth- bit time slot), either at the end of a byte write or a sequential write, th e internal write cycle is triggered. a stop condition at any other time slot does not trigger th e internal write cycle. after the stop condition, the delay t w , and the successful completion of a write operation, the device?s internal address counter is increm ented automatically, to point to the next byte address after the last one that was modified. after an unsuccessful write operation, st25 dvxxx enters in i2c dead state: internal address counter is not incremen ted, and st25dvxxx is waiting for a full new i2c instruction. during the internal write cycle, the serial data (sda) signal is disabled internally, and the device does not respond to any requests. caution: i 2 c writing data in user or system memory (eeprom), transit via the 256-bytes fast transfer mode's buffer. consequently fast transf er mode must be deactivated before starting any write operation in user or system memory, otherw ise command will be notack, programming is not done and device goes in standby mode. table 52. operating modes mode rw bit bytes initial sequence current address read 1 1 start, device select, rw = 1 random address read 0 1 start, device select, rw = 0, address 1 restart, device select, rw = 1 sequential read 1 1 similar to current or random address read byte write 0 1 start, device select, rw = 0 sequential write 0 256 byte start, device select, rw = 0 table 53. address mo st significant byte b15 b14 b13 b12 b11 b10 b9 b8 table 54. address least significant byte b7 b6 b5 b4 b3 b2 b1 b0 i 2 c operation ST25DV04K st25dv16k st25dv64k 90/220 docid027603 rev 4 6.4.1 i 2 c byte write after the device select code and the address by tes, the bus master sends one data byte. if byte write is not inhibited, the device replies with ack. if byte write is inhibited, th e device replies with noack. the bus master terminates the transfer by generating a stop condition (see figure 26: write mode sequences when write is not inhibited ). for byte write in eeprom (use r memory or system configur ation), internal programming starts after the ack, for a duration of t w (as defined in table 209: i 2 c ac characteristics up to 85c and table 210: i 2 c ac characteristics up to 125c ). for writes in fast transfer mode buffer or dyna mic registers, internal programming is done at the ack. if byte write is inhibited, the device replie s with noack. the bus master terminates the transfer by generating a stop condition and byte location not is modified (see figure 27: write mode sequences wh en write is inhibited ). byte write is inhibited if byte complie s with one of the following conditions: ? byte is in user memory and is writ e protected with lock_ccfile register. ? byte is in user memory and is writ e protected with i2c ss register, and i 2 c security session is closed. ? byte is in user memory and fa st transfer mode is activated. ? byte is in system memory and is a read only register. ? byte is in system memory and i 2 c security session is closed. ? byte is in fast transfer mode?s mailbox and is not the first byte of mailbox. ? byte is in fast transfer mo de?s mailbox and mailbox is busy. ? byte is in fast transfer mode?s mailbox and fast transfer mode is not activated. ? byte is in dynamic registers area and is a read only register. 6.4.2 i 2 c sequential write the i 2 c sequential write allows up to 256 bytes to be written in one command, provided they are all located in the same user memory area or are all located in writable addresses. after each byte is transfer red, the internal byte address counter is incremented. for each byte sent by the bus master: ? if byte write is not inhibited, the device replies with ack. ? if byte write is inhibited, the device rep lies with noack. the transfer is terminated by the bu s master generating a stop condition: ? for writes in eeprom (user memory or sys tem configuration), if all bytes have been ack'ed, internal programming of all bytes starts after the last ack, for a duration dependent on the number of bytes to write (see below). ? for writes in fast transfer mode buffer or dynamic registers, if all bytes have been ack'ed, internal programming is done at the ack. ? if some bytes have been notack?ed, no internal programming is done (0 byte written). docid027603 rev 4 91/220 ST25DV04K st25dv16k st25dv64k i 2 c operation 219 byte write is inhibited if byte complies with conditions described in section 6.4.1: i 2 c byte write , in addition: ? byte is in user memory but does not belong to same area than previous received byte (area border crossing is forbidden). ? 256 write occurrence have already been re ached in the same sequential write. eeprom memory (user memory a nd system configurat ion) is internally organized in pages of 4 bytes long. data located in a same page all share the same most significant memory address bits b16-b2. i 2 c sequential write pr ogramming time in the eeprom memory is dependent on this internal organization: total programming time is the i 2 c write time t w (as defined in table 209: i 2 c ac characteristics up to 85c and table 210: i 2 c ac characteristics up to 125c ) multiplied by the number of internal eeprom pages where the data must be programmed, including incomplete pages. for example, a 256 bytes i 2 c sequential write, starting at address 0002h will wr ite data over 65 pages. total write time in this case is t w x 65. figure 26. write mode sequences when write is not inhibited note: n 256 6 w r s 6 w d u w % \ w h : u l w h ' h y 6 h o h f w % \ w h d g g u h v v % \ w h d g g u h v v ' d w d l q 6 w d u w 6 h t x h q w l d o : u l w h ' h y 6 h o h f w % \ w h d g g u h v v % \ w h d g g u h v v ' d w d l q ' d w d l q 0 6 y 9 6 w r s ' d w d l q 1 $ & . 5 : $ & . $ & . $ & . $ & . $ & . $ & . $ & . 5 : $ & . $ & . i 2 c operation ST25DV04K st25dv16k st25dv64k 92/220 docid027603 rev 4 figure 27. write mode sequences when write is inhibited note: n 256 6.4.3 minimizing system delays by polling on ack during the internal write cycle, the device disconnects itself from the bus, and writes a copy of the data from its internal latches to the memory cells. the maximum i2c write time (t w ) is shown in table 209: i 2 c ac characteristics up to 85c and table 210: i 2 c ac characteristics up to 125c , but the typical time is shorter. to make use of this, a polling sequence can be used by the bus master. the sequence, as shown in figure 28: write cycle polling flowchart using ack , is: ? initial condition: a write cycle is in progress. ? step 1: the bus master issues a start condi tion followed by a device select code (the first byte of the new instruction). ? step 2: if the device is busy with the internal write cycle, no ack is returned and the bus master goes back to step 1. if the device ha s terminated the intern al write cycle, it responds with an ack, indicating that the devi ce is ready to receive the second part of the instruction (the first byte of this in struction having been sent during step 1). note: there is no need of polling when writin g in dynamic registers or in mailbox, since programming time is null. 6 w r s 6 w d u w % \ w h : u l w h ' h y v h o h f w % \ w h d g g u h v v % \ w h d g g u h v v ' d w d l q 6 w d u w 6 h t x h q w l d o : u l w h ' h y v h o h f w % \ w h d g g u h v v % \ w h d g g u h v v ' d w d l q ' d w d l q 0 6 y 9 6 h t x h q w l d o : u l w h f r q w g 6 w r s ' d w d l q 1 $ & . $ & . $ & . 1 2 $ & . 5 : $ & . $ & . $ & . 1 2 $ & . 5 : 1 2 $ & . 1 2 $ & . docid027603 rev 4 93/220 ST25DV04K st25dv16k st25dv64k i 2 c operation 219 figure 28. write cycle polling flowchart using ack 0 6 y 9 : u l w h f \ f o h l q s u r j u h v v 1 h [ w 2 s h u d w l r q l v d g g u h v v l q j w k h p h p r u \ 6 w d u w f r q g l w l r q ' h y l f h v h o h f w z l w k 5 : $ & . u h w x u q h g < ( 6 1 2 < ( 6 1 2 6 w r s ' d w d i r u w k h : u l w h r s h u d w l r q 6 h q g $ g g u h v v d q g 5 h f h l y h $ & . < ( 6 1 2 6 w d u w & r q g l w l r q & r q w l q x h w k h : u l w h r s h u d w l r q & r q w l q x h w k h 5 d q g r p 5 h d g r s h u d w l r q ' h y l f h v h o h f w z l w k 5 : ) l u v w e \ w h r i l q v w u x f w l r q z l w k 5 : d o u h d g \ g h f r g h g e \ w k h g h y l f h i 2 c operation ST25DV04K st25dv16k st25dv64k 94/220 docid027603 rev 4 6.5 i 2 c read operations read operation in user memory is performed successfully only if: ? area to which the byte belongs is not read protected by i2css register. ? area to which the byte belongs is read protected by i2css register, but i 2 c security session is open. read operations in system memory and dyna mic registers are done independently of any protection mechanism, except i2c_pwd register which needs i 2 c security session to be open first. read operation in fast transfer mode?s mailbox is performed successfully only if fast transfer mode is activated. if read is not successful, st25 dvxxx releases the bus and i 2 c host reads byte value ffh. after the successful completion of a read operat ion, the device?s internal address counter is incremented by one, to point to the next byte address. after an unsuccessful read operation, st25dvxxx enters in i 2 c dead state: internal address counter is not incremented, and st 25dvxxx is waiting for a full new i 2 c instruction. 6.5.1 random address read a dummy write is first performed to load the address into this address counter (as shown in figure 29: read mode sequences ) but without sending a stop condition. then, the bus master sends another start condition, and repeats the device select code, with the read/ write bit (r w ) set to 1. the device acknowledges this, and outputs the contents of the addressed byte. the bus master must not acknowledge the byte, and terminates the transfer with a stop condition. 6.5.2 current address read for the current address read operation, following a start condition, the bus master only sends a device select code with the read/ write bit (r w ) set to 1. the device acknowledges this, and outputs the byte addressed by the in ternal address counter. the counter is then incremented. the bus master terminates the transfer with a stop condition , as shown in figure 29: read mode sequences , without acknowledging the byte. docid027603 rev 4 95/220 ST25DV04K st25dv16k st25dv64k i 2 c operation 219 figure 29. read mode sequences 6.5.3 sequential read access this operation can be used after a current address read or a random address read. the bus master does acknowledge the data byte output, and sends additional clock pulses so that the device continues to output the next by te in sequence. to terminate the stream of bytes, the bus master must not acknowledge the last byte, and must generate a stop condition, as shown in figure 29: read mode sequences . the output data comes from consecutive addresses, with the internal address counter automatically incremented after each byte output. sequential read in user memory: ? sequential read cannot cross area borders. after reaching area border, device continues to output ffh ? there is no roll over inside area or at the end of user memory (st25dvxxx returns only ffh after last user memory byte address). 6 w d u w ' h y v h o % \ w h d g g u % \ w h d g g u 6 w d u w ' h y v h o ' d w d r x w $ , h ' d w d r x w 1 6 w r s 6 w d u w & x u u h q w $ g g u h v v 5 h d g ' h y v h o ' d w d r x w 5 d q g r p $ g g u h v v 5 h d g 6 w r s 6 w d u w ' h y v h o ' d w d r x w 6 h t x h q w l d o & x u u h q w 5 h d g 6 w r s ' d w d r x w 1 6 w d u w ' h y v h o % \ w h d g g u % \ w h d g g u 6 h t x h q w l d o 5 d q g r p 5 h d g 6 w d u w ' h y v h o ' d w d r x w 6 w r s $ & . 5 : 1 2 $ & . $ & . 5 : $ & . $ & . $ & . 5 : $ & . $ & . $ & . 1 2 $ & . 5 : 1 2 $ & . $ & . $ & . $ & . 5 : $ & . $ & . 5 : $ & . 1 2 $ & . i 2 c operation ST25DV04K st25dv16k st25dv64k 96/220 docid027603 rev 4 sequential read in system memory: ? there is no roll over after reaching end of system memory (st25dv returns only ffh after last system memory byte address). ? sequential read in dynamic registers: ? it is possible to read sequentially dynamic registers and fast transfer mode?s mailbox (contiguous i 2 c addresses). sequential read in dynamic registers: ? there is no roll over at the end of the mailbox (st25dv returns only ffh after last system memory byte address). 6.5.4 acknowledge in read mode for all read commands, the device waits, after each byte read, for an acknowledgment during the ninth bit time. if the bus master does not drive serial data (sda) low during this time, the device terminates the data transfer and switches to its standby mode. docid027603 rev 4 97/220 ST25DV04K st25dv16k st25dv64k i 2 c operation 219 6.6 i 2 c password management the st25dvxxx controls i 2 c security session using an i 2 c 64-bit password. this i 2 c password is managed with two i 2 c dedicated commands: i 2 c present password and i 2 c write password. 6.6.1 i 2 c present password command description the i 2 c present password command is used in i 2 c mode to present the password to the st25dvxxx. this is used to open i 2 c security session or to allow i 2 c password modification (see section 5.6: data protection for detailed explanation about password usage). following a start condition, the bus master sends a device select code with the read/ write bit (r w ) reset to 0 and the chip enable bit e2 at 1. the device acknowledges this, as shown in figure 30: i 2 c present password sequence , and waits for two i 2 c password address bytes, 09h and 00h. the device responds to each address byte with an acknowledge bit, and then waits for the eight password data bytes, the validation code, 09h, and a resend of the eight password data bytes. the most signif icant byte of the password is sent first, followed by the least significant bytes. it is necessary to send the 64-b it password twice to prevent any data corruption during the sequence. if the two 64-bit passwords sent are not exactly the sa me, the st25dvxxx does not start the internal comparison. when the bus master generates a stop condit ion immediately after the ack bit (during the tenth bit time slot), an internal delay equival ent to the write cycle time is triggered. a stop condition at any other time does not trigger the internal delay. during that delay, the st25dvxxx compares the 64 received data bits with the 64 bits of the stored i 2 c password. if the values match, the i 2 c security session is open after the internal delay, and the i2c_sso_dyn register is set to 01h. if the values do not match, the i 2 c security session is closed and i2c_sso_dyn register is set to 00h. during the internal delay, the serial data (sda ) signal is disabled internally, and the device does not respond to any requests. i2c_sso_dyn is a dynamic regi ster, it can be checked via i 2 c host to know if i 2 c security session is open. figure 30. i 2 c present password sequence 0 6 y 9 6 w d u w ' h y l f h v h o h f w f r g h 3 d v v z r u g > @ $ f n 5 : $ f n $ f n $ f n ' h y l f h v h o h f w f r g h $ f n j h q h u d w h g g x u l q j w k e l w w l p h v o r w $ f n $ f n $ f n 6 w r s $ f n $ f n $ f n $ f n $ f n $ f n $ f n $ f n 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ $ f n $ f n $ f n $ f n 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g $ g g u h v v k 3 d v v z r u g $ g g u h v v k 9 d o l g d w l r q f r g h k $ f n $ f n 3 d v v z r u g > @ $ f n 3 d v v z r u g > @ i 2 c operation ST25DV04K st25dv16k st25dv64k 98/220 docid027603 rev 4 6.6.2 i 2 c write password command description the i 2 c write password command is used to update the i 2 c password value (register i2c_pwd). it cannot be used to update any of the rf passwords. after the write cycle, the new i 2 c password value is automatically activated. the i 2 c password value can only be modified after issuing a valid i 2 c present password command. following a start condition, the bus master sends a device select code with the read/ write bit (r w ) reset to 0 and the chip enable bit e2 at 1. the device acknowledges this, as shown in figure 31: i 2 c write password sequence , and waits for the two i 2 c password address bytes, 09h and 00h. the device responds to each address byte with an acknowledge bit, and then waits for the four password data bytes, the validation code, 07h, and a resend of the eight password data bytes. the most signif icant byte of the password is sent first, followed by the least significant bytes. it is necessary to send twice the 64-bit password to prevent any data corruption during the write sequence. if the two 64-b it passwords sent are not exactly the same, the st25dvxxx does not modify the i 2 c password value. when the bus master generates a stop condit ion immediately after the ack bit (during the tenth bit time slot), the internal write cycle is triggered. a stop condition at any other time does not trigger the internal write cycle. during the internal write cycle, the serial data (sda) signal is disabled internally, and the device does not respond to any requests. caution: i 2 c write password command data transits via the 256-bytes fast transfer mode's buffer. consequently fast transfer mode must be deactivated before issuing a write password command, otherwise command is notack (after address lsb), and programming is not done and device goes in standby mode. figure 31. i 2 c write password sequence 0 6 y 9 6 w d u w ' h y l f h v h o h f w f r g h 3 d v v z r u g > @ $ f n 5 : $ f n $ f n $ f n ' h y l f h v h o h f w f r g h $ f n j h q h u d w h g g x u l q j w k e l w w l p h v o r w $ f n $ f n $ f n 6 w r s $ f n $ f n $ f n $ f n $ f n $ f n $ f n $ f n 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ $ f n $ f n $ f n $ f n 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g > @ 3 d v v z r u g $ g g u h v v k 3 d v v z r u g $ g g u h v v k 9 d o l g d w l r q f r g h k $ f n 3 d v v z r u g > @ $ f n 3 d v v z r u g > @ docid027603 rev 4 99/220 ST25DV04K st25dv16k st25dv64k rf operations 219 7 rf operations contactless exchanges are performed in rf mode as specified by iso/iec 15693 or nfc forum type 5. the st25dvxxx communicates via the 13.56 mhz carrier electromagnetic wave on which incoming data are demodulated from the received signal amplitude modulation (ask: amplitude shift keying). the received ask wave is 10% or 100% modulated with a data rate of 1.6 kbit/s using the 1/256 pulse coding mode or a data rate of 26 kbit/s using the 1/4 pulse coding mode. outgoing data are generated by the st25dvxx x load variation usi ng manchester coding with one or two subcarrier frequencies at 423 khz and 484 khz. data are transferred from the st25dvxxx at 6.6 kbit/s in low data rate mode and 26 kbit/s in high data rate mode. the st25dvxxx supports the 53 kbit/s in high da ta rate mode in one subcarrier frequency at 423 khz. the st25dvxxx follows iso/iec 15693 or nf c forum type 5 recommendation for radio- frequency power and signal interface and for anticollision and transmission protocol. 7.1 rf communication 7.1.1 access to a iso/iec 15693 device the dialog between the ?rf reader? and the st25dvxxx takes place as follows: these operations use the rf power transfer and communication signal interface described below (see power transfer, frequency and operating field). this technique is called rtf (reader talk first). ? activation of the st25dvxxx by the rf operating fiel d of the reader, ? transmission of a command by the reader (st25dvxxx detects carrier amplitude modulation) ? transmission of a response by the st25dv xxx(st25dvxxx modulates is load clocked at subcarrier rate) operating field the st25dvxxx operates contin uously between the minimum and maximum values of the electromagnetic field h defined in table 214: rf characteristics . the reader has to generate a field within these limits. power transfer power is transferred to the st25dvxxx by radio frequency at 13.56 mhz via coupling antennas in the st25dvxxx and the reader. the rf operating field of the reader is transformed on the st25dvxxx antenna to an ac voltage which is rectified, filtered and internally regulated. during communications, the amplitude modulation (ask) on this received signal is demodu lated by the ask demodulator rf operations ST25DV04K st25dv16k st25dv64k 100/220 docid027603 rev 4 frequency the iso 15693 standard defines the carrier frequency (f c ) of the operating field as 13.56 mhz 7 khz. 7.2 rf communication and energy harvesting as the current consumption can affect the ac signal delivered by the antenna, rf communications with st25dvxxx are not guarant eed during voltage delivery on the energy harvesting analog output v_eh. rf communication can disturb and possibly stop energy harvesting mode. 7.3 fast transfer mode mailbox access in rf thanks to dedicated commands, the rf interface has the possibility to check mailbox availability, and the capability to access it di rectly to put or get a message from it (see section 5.1: fast transfer mode (ftm) for specific features). 7.4 rf protocol description 7.4.1 protocol description the transmission protocol (or simply ?the protocol?) defines the mechanism used to exchange instructions and data between the vcd (vicinity coup ling device) and the st25dvxxx in both directions. it is bas ed on the concept of ?vcd talks first?. this means that a st25dvxxx does not star t transmitting unless it has received and properly decoded an instruction sent by the vcd. the protocol is based on an exchange of: ? a request from the vcd to the st25dvxxx, ? a response from the st25dvxxx to the vcd. each request and each response are contained in a frame. the frame are delimited by a start of frame (sof) and end of frame (eof). the protocol is bit-oriented. the number of bits transmitted in a frame is a multiple of eight (8), that is an inte ger number of bytes. a single-byte field is transmitted least signific ant bit (lsbit) first. a multiple-byte field is transmitted least significant byte (lsbyte) first and each byte is transmitted least significant bit (lsbit) first. docid027603 rev 4 101/220 ST25DV04K st25dv16k st25dv64k rf operations 219 7.4.2 st25dvxxx states re ferring to rf protocol the st25dvxxx can be in one of four states: ? power-off ? ready ? quiet ? selected transitions between these states are specified in figure 33: st25dvxxx state transition diagram and table 55: st25dvxxx response depending on request_flags . power-off state the st25dvxxx is in the power-off state when it does not receive en ough energy from the vcd. ready state the st25dvxxx is in the ready st ate when it receives enough energy from the vcd. when in the ready state, the st25dvxxx answers an y request where the select_flag is not set. quiet state when in the quiet state, the st25dvxxx answers any request with the address_flag set, except for inventory requests. selected state in the selected state, the st25dvxxx answers any request in all modes (see section 7.4.3: modes ): ? request in select mode with the select_flag set ? request in addressed mode if the uid matches ? request in non-addressed mode as it is the mode for general requests figure 32. st25dvxxx protocol timing vcd request frame request frame st25dvx xx response frame response frame timing <-t 1 -> <-t 2 -> <-t 1 -> <-t 2 -> rf operations ST25DV04K st25dv16k st25dv64k 102/220 docid027603 rev 4 figure 33. st25dvxxx state transition diagram 1. the st25dvxxx returns to the power off state if the tag is out of the rf field for at least t rf_off . the intention of the state transition method is that only one st25dvxxx should be in the selected state at a time. when the select_flag is set to 1, the request shall not contain a unique id. when the address_flag is set to 0, the request shall not contain a unique id. table 55. st25dvxxx response depending on request_flags flags address_flag select_flag 1 addressed 0 non addressed 1 selected 0 non selected st25dvxxx in ready or selected state (devices in quiet state do not answer) -x-x st25dvxxx in selected state - x x - st25dvxxx in ready, quiet or selected state (the device which matches the uid) x- -x error (03h) or no response (command dependent) x-x- 0 6 y 9 , q 5 ) i l h o g 6 w d \ t x l h w 8 , ' 6 h o h f w 8 , ' $ q \ r w k h u f r p p d q g 6 w d \ t x l h w 8 , ' 6 h o h f w 8 , ' 5 h v h w w r u h d g \ , q y h q w r u \ 2 x w r i 5 ) i l h o g d i w h u w 5 ) b 2 ) ) 2 x w r i 5 ) i l h o g d i w h u w 5 ) b 2 ) ) 2 x w r i i l h o g d i w h u w 5 ) b 2 ) ) $ q \ r w k h u f r p p d q g z k h u h w k h $ g g u h v v b ) o d j l v v h w $ 1 ' z k h u h w k h , q y h q w r u \ b ) o d j l v q r w v h w $ q \ r w k h u f r p p d q g z k h u h 6 h o h f w b ) o d j l v q r w v h w 5 h v h w w r u h d g \ z k h u h 6 h o h f w b ) o d j l v v h w r u 6 h o h f w z l w k 8 , ' 3 r z h u r i i 5 h d g \ 4 x l h w 6 h o h f w h g docid027603 rev 4 103/220 ST25DV04K st25dv16k st25dv64k rf operations 219 7.4.3 modes the term ?mode? refers to the mechanism used in a request to specify the set of st25dvxxx devices that shall execute the request. addressed mode when the address_flag is set to 1 (addressed mode), the request contains the unique id (uid) of the addressed st25dvxxx. any st25dvxxx that receives a request with the address_flag set to 1 compares the received unique id to its own. if it matche s, then the st25dvxxx ex ecutes the request (if possible) and returns a response to the vcd as specified in the command description. if the uid does not match, then it remains silent. non-addressed mode (general request) when the address_flag is cleared to 0 (non-addressed mode), the request does not contain a unique id. select mode when the select_flag is set to 1 (select mode ), the request does not contain a unique id. the st25dvxxx in the selected st ate that receives a request with the select_flag set to 1 executes it and returns a response to the vcd as specified in the command description. only the st25dvxxx in the selected state answer s a request where the se lect_flag is set to 1. the system design ensures that only one st25dv xxx can be in the select state at a time. 7.4.4 request format the request consists of: ? an sof, ? flags, ? a command code, ? parameters and data, ? a crc, ? an eof. 7.4.5 request flags in a request, the ?flags? field specifies t he actions to be performe d by the st25dvxxx and whether corresponding fields are present or not. the flags field consists of eight bits. bit 3 (i nventory_flag) of the request flag defines the contents of the four msbs (bit s 5 to 8). when bit 3 is reset (0), bits 5 to 8 define the table 56. general request format s o f request_flags command code parameters data 2 byte crc e o f rf operations ST25DV04K st25dv16k st25dv64k 104/220 docid027603 rev 4 st25dvxxx selection criteria. when bit 3 is se t (1), bits 5 to 8 define the st25dvxxx inventory parameters. . table 57. definition of request flags 1 to 4 bit no flag level description bit 1 subcarrier_flag (1) 1. subcarrier_flag refers to th e st25dvxxx-to-vcd communication. 0 a single subcarrier frequency is used by the st25dvxxx 1 two subcarriers are used by the st25dvxxx bit 2 data_rate_flag (2) 2. data_rate_flag refers to the st25dvxxx-to-vcd communication. 0 low data rate is used 1 high data rate is used bit 3 inventory_flag 0 the meaning of flags 5 to 8 is described in table 58: request flags 5 to 8 when inventory_flag, bit 3 = 0 1 the meaning of flags 5 to 8 is described in table 59: request flags 5 to 8 when inventory_flag, bit 3 = 1 bit 4 protocol_extension_flag 0 no protocol format extension 1 protocol format extension. reserved for future use. table 58. request flags 5 to 8 when inventory_flag, bit 3 = 0 bit nb flag level description bit 5 select flag (1) 1. if the select_flag is set to 1, the address_flag is set to 0 and the uid fi eld is not present in the request. 0 the request is executed by any st25dvxxx according to the setting of address_flag 1 the request is executed only by the st25dvxxx in selected state bit 6 address flag 0 the request is not addressed. uid fi eld is not present. the request is executed by all st25dvxxxs. 1 the request is addressed. uid field is present. the request is executed only by the st25dvxxx whose uid matc hes the uid specified in the request. bit 7 option flag 0 option not activated. 1 option activated. bit 8 rfu 0 - docid027603 rev 4 105/220 ST25DV04K st25dv16k st25dv64k rf operations 219 7.4.6 response format the response consists of: ? an sof, ? flags, ? parameters and data, ? a crc, ? an eof. 7.4.7 response flags in a response, the flags indicate how actions have been performed by the st25dvxxx and whether corresponding fields are present or not. the response flags consist of eight bits. table 59. request flags 5 to 8 when inventory_flag, bit 3 = 1 bit nb flag level description bit 5 afi flag 0 afi field is not present 1 afi field is present bit 6 nb_slots flag 0 16 slots 11 slot bit 7 option flag 0 - bit 8 rfu 0 - table 60. general response format s o f response_flags parameters data 2 byte crc e o f table 61. definitions of response flags 1 to 8 bit nb flag level description bit 1 error_flag 0 no error 1 error detected. error code is in the ?error? field. bit 2 rfu 0 - bit 3 rfu 0 - bit 4 extension flag 0 no extension bit 5 rfu 0 - bit 6 rfu 0 - bit 7 rfu 0 - bit 8 rfu 0 - rf operations ST25DV04K st25dv16k st25dv64k 106/220 docid027603 rev 4 7.4.8 response and error code if the error_flag is set by the st25dvxxx in the response, the error code field is present and provides information about the error that occurred. error codes not specified in table 62: response error code definition are reserved for future use. 7.5 timing definition t 1 : st25dvxxx response delay upon detection of the rising edge of the eof received from the vcd, the st25dvxxx waits for a t 1nom time before transmitting its response to a vcd request or switching to the next slot during an inventory process. values of t 1 are given in table 63: timing values . t 2 : vcd new request delay t 2 is the time after which the vcd may send an eof to switch to the next slot when one or more st25dvxxx responses have been received during an inventory command. it starts from the reception of the eof from the st25dvxxxs. the eof sent by the vcd may be either 10% or 100% modulated regardless of the modulation index used for transmitting the vcd request to the st25dvxxx. t 2 is also the time after which the vcd ma y send a new request to the st25dvxxx, as described in figure 32: st25dvxxx protocol timing . values of t 2 are given in table 63: timing values . t 3 : vcd new request delay when no response is received from the st25dvxxx t 3 is the time after which the vcd may send an eof to switch to the next slot when no st25dvxxx response has been received. the eof sent by the vcd may be either 10% or 100% modulated regardless of the modulation index used for transmitting the vcd request to the st25dvxxx . table 62. response error code definition error code meaning 01h command is not supported. 02h command is not recognized (format error). 03h the option is not supported. 0fh error with no information given. 10h the specified block is not available. 11h the specified block is already locked and thus cannot be locked again. 12h the specified block is locked and its contents cannot be changed. 13h the specified block was not successfully programmed. 14h the specified block wa s not successfully locked. 15h the specified block is protected in read. docid027603 rev 4 107/220 ST25DV04K st25dv16k st25dv64k rf operations 219 from the time the vcd has generated the rising edge of an eof: ? if this eof is 100% modulated, the vcd waits for a time at least equal to t 3min for 100% modulation before sending a new eof. ? if this eof is 10% modulated, the vcd waits for a time at least equal to t 3min for 10% modulation before sending a new eof. table 63. timing values (1) minimum (min) values nominal (nom) values maximum (max) values 100% modulation 10% modulation t 1 4320 / f c = 318.6 s 4352 / f c = 320.9 s 4384 / f c = 323.3 s (2) t 2 4192 / f c = 309.2 s no t nom no t max t 3 t 1max (3)(3) + t sof (4) t 1max (3) + t nrt (5) + t 2min no t nom no t max 1. the tolerance of specific timings is 32/f c . 2. vcd request will not be interpreted during the first milliseconds following the rf field rising. 3. t 1max does not apply for write-alike requ ests. timing conditions for write-alike requests are defined in the command description. 4. t sof is the time taken by the st25dvxx x to transmit an sof to the vcd. t sof depends on the current data rate: high data rate or low data rate. 5. t nrt is the nominal response time of the st25dvxxx. t nrt depends on v icc to st25dvxxx data rate and subcarrier modulation mode. rf operations ST25DV04K st25dv16k st25dv64k 108/220 docid027603 rev 4 7.6 rf commands 7.6.1 rf command code list the st25dvxxx supports the following le gacy and extended rf command set: ? inventory , used to perform t he anticollision sequence. ? stay quiet , used to put the st25dvxxx in quiet mode, where it does not respond to any inventory command. ? select , used to select the st25dvxxx. after this command, the st25dvxxx processes all read/write commands with select_flag set. ? reset to ready , used to put the st25dvxxx in the ready state. ? read single block and extended read single block , used to output the 32 bit of the selected block and its locking status. ? write single block and extended write single block , used to write and verify the new content for an update of a 32 bit block, provided that it is not in a locked memory area. ? read multiple blocks and extended read multiple block , used to read the selected blocks in an unique area, and send back their value. ? write multiple blocks and extended write multiple block , used to write and verify the new content for an update of up to 4 blocks located in the same memory area, which was not previously locked for writing. ? write afi , used to write the 8-bit value in the afi register. ? lock afi , used to lock the afi register. ? write dsfid , used to write the 8-bit value in the dsfid register. ? lock dsfid , used to lock the dsfid register. ? get system information and extended get system information , used to provide the system information value. ? get system information , used to provide the standard system information values. ? extended get system information , used to provide the extended system information values. ? write password , used to update the 64 bit of the selected areas or configuration password, but only after presenting the current one. ? lock block and extended lock block , used to write the cc file blocks security status bits (protect the cc file content against writing). ? present password , enables the user to present a password to open a security session. ? fast read single block and fast extended read single block, used to output the 32 bits of the selected block and its locking status at doubled data rate. ? fast read mult iple blocks and fast extended read multiple blocks , used to read the selected blocks in a single area and send back their value at doubled data rate. ? read message , used to output up to 256 byte of the mailbox. ? read message length , used to output the mailbox message length. ? fast read message , used to output up to 256 byte of the mailbox, at double data rate. ? write message , used to write up to 256 byte in the mailbox. ? fast read message length, used to ouput the mailbox length, at double data rate. docid027603 rev 4 109/220 ST25DV04K st25dv16k st25dv64k rf operations 219 ? fast write message, used to write up to 256 bytes in the mailbox, with answer at double data rate. ? read configuration , used to read static configuration registers. ? write configuration , used to write static configuration registers. ? read dynamic configuration, used to read dynamic register. ? write dynamic configuration, used to write dynamic register. ? fast read dynamic configuration , used to read dynamic register, at double data rate. ? fast write dynamic configuration , used to write dynamic register, with answer at double data rate. ? manage gpo, used to drive gpo output value when corresponding gpo mode is enabled. rf operations ST25DV04K st25dv16k st25dv64k 110/220 docid027603 rev 4 7.6.2 command codes list the st25dvxxx supports the comma nds described in this sectio n. their codes are given in table 64 . - table 64. command codes command code standard function command code custom function 01h inventory a0h read configuration 02h stay quiet a1h write configuration 20h read single block a9h manage gpo 21h write single block aah write message 22h lock block abh read message length 23h read multiple blocks ach read message 24h write multiple blocks adh read dynamic configuration 25h select aeh write dynamic configuration 26h reset to ready b1h write password 27h write afi b3h present password 28h lock afi c0h fast read single block 29h write dsfid c3h fast read multiple blocks 30h extended read single block c4h fast extended read single block 31h extended write single block c5h fast extended read multiple block 32h extended lock block cah fast write message 33h extended read multiple blocks cbh fast read message length 34h extended write multiple blocks cch fast read message 2ah lock dsfid cdh fast read dynamic configuration 2bh get system info ceh fast write dynamic configuration 2ch get multiple bl ock security status 3bh extended get system info 3ch extended get multiple block security status docid027603 rev 4 111/220 ST25DV04K st25dv16k st25dv64k rf operations 219 7.6.3 general command rules in case of a valid command, the following paragraphs will describe t he expected behavior for each command. but in case of an invalid command, in a general manner, the st 25dvxxx will behave as follows: 1. if flag usage is incorrect, th e error code 03h will be issued on ly if the right uid is used in the command, otherwise no response will be issued. 2. error 02h will be issued if the custom command is used with the manufacturer code different from the st one another case is if i 2 c is busy. in this case, any rf co mmand (except inventory, select, stay quiet and reset to ready) will get 0fh error code as response only: a) if select flag and address flags are not set at the same time (except if st25dvxxx is in quiet state) b) if select flag is set and st25dvxxx is in selected state. for all other commands, if i 2 c is busy, no response w ill be issued by st25dvxxx. 7.6.4 inventory upon receiving the inventory request, the st 25dvxxx runs the antico llision sequence. the inventory_flag is set to 1. the meaning of flags 5 to 8 is shown in table 59: request flags 5 to 8 when inventory_flag, bit 3 = 1 . the request contains: ? the flags ? the inventory command code (001) ? the afi if the afi flag is set ? the mask length ? the mask value if mask length is different from 0 ? the crc the st25dvxxx does not generate any answer in case of error. the response contains: ? the flags ? the unique id table 65. inventory request format request sof request_flag s inventory optional afi mask length mask value crc16 request eof - 8 bits 01h 8 bits 8 bits 0 - 64 bits 16 bits - table 66. inventory response format response sof response_flags dsfid uid crc16 response eof - 8 bits 8 bits 64 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 112/220 docid027603 rev 4 during an inventory process, if the vcd do es not receive an rf st25dvxxx response, it waits for a time t 3 before sending an eof to switch to the next slot. t 3 starts from the rising edge of the request eof sent by the vcd. ? if the vcd sends a 100% modulated eof, the minimum value of t 3 is: t 3 min = 4384/f c (323.3s) + t sof ? if the vcd sends a 10% modulated eof, the minimum value of t 3 is: t 3 min = 4384/f c (323.3s) + t nrt + t 2min where: ? t sof is the time required by the st25d vxxx to transmit an sof to the vcd, ? t nrt is the nominal response time of the st25dvxxx. t nrt and t sof are dependent on the st25dvxxx-to-vcd data rate and subcarrier modulation mode. note: in case of error, no res ponse is sent by st25dvxxx. 7.6.5 stay quiet on receiving the stay quiet command, the st 25dvxxx enters the quiet state if no error occurs, and does not send back a response. there is no response to the stay quiet command even if an error occurs. the option_flag is not supported. the inventory_flag must be set to 0. when in the quiet state: ? the st25dvxxx does not process any re quest if the inventory_flag is set, ? the st25dvxxx processes any addressed request. the st25dvxxx exits the quiet state when: ? it is reset (power off), ? receiving a select request. it t hen goes to the selected state, ? receiving a reset to ready request. it then goes to the ready state. the stay quiet command must always be executed in addressed mode (select_flag is reset to 0 and address_flag is set to 1). table 67. stay quiet request format request sof request flags stay quiet uid crc16 request eof - 8 bits 02h 64 bits 16 bits - docid027603 rev 4 113/220 ST25DV04K st25dv16k st25dv64k rf operations 219 7.6.6 read single block on receiving the read single block command, the st25dvxxx reads the requested block and sends back its 32-bit value in the response. the option_flag is supported, when set response include the block security status . the inventory_flag must be set to 0. block number is coded on 1 byte and only first 256 blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. request parameters: ? request flags ? uid (optional) ? block number response parameters: ? block security status if option_flag is set (see table 70: block security status ) ? four bytes of block data figure 34. stay quiet frame exchange between vcd and st25dvxxx vcd sof stay quiet request eof st25dvxxx table 68. read single block request format request sof request_flags read single block uid (1) 1. gray color means that the field is optional. block number crc16 request eof -8 bits 20h 64 bits 8 bits 16 bits - table 69. read single block response format when error_flag is not set response sof response_flags block security status (1) 1. gray color means that the field is optional. data crc16 response eof -8 bits 8 bits 32 bits 16 bits - table 70. block security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use. all at 0. 0: current block not locked 1: current block locked rf operations ST25DV04K st25dv16k st25dv64k 114/220 docid027603 rev 4 response parameter: ? error code as error_flag is set ? 03h: command option not supported ? 0fh: error with no information ? 10h: the specified block is not available ? 15h: the specified block is read-protected 7.6.7 extended read single block on receiving the extended read single block command, the st25dvxxx reads the requested block and sends back its 32-bit value in the response. when the option_flag is set, the response includes the block security status. block number is coded on 2 bytes so a ll memory blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. request parameters: ? request flags ? uid (optional) ? block number table 71. read single block response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 35. read single block frame exchange between vcd and st25dvxxx vcd sof read single block request eof st25dvxxx <-t 1 -> sof read single block response eof table 72. extended read single block request format request sof request_flags extended read single block uid (1) 1. gray color means that the field is optional. block number crc16 request eof -8 bits 30h 64 bits 16 bits 16 bits - docid027603 rev 4 115/220 ST25DV04K st25dv16k st25dv64k rf operations 219 response parameters: ? block security status if option_flag is set (see table 70: block security status ) ? four bytes of block data response parameter: ? error code as error_flag is set ? 03h: command option not supported or no response ? 0fh: error with no information ? 10h: the specified block is not available ? 15h: the specified block is read-protected 7.6.8 write single block on receiving the write single block command, the st25dvxxx writes the data contained in the request to the targeted block and reports whether the write operat ion was successful in the response. when the option_f lag is set, wait for eof to respond. the inventory_flag must be set to 0. table 73. extended read single block response format when error_flag is not set response sof response_flags block security status (1) 1. gray color means that the field is optional. data crc16 response eof -8 bits 8 bits 32 bits 16 bits - table 74. block security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use. all at 0. 0: current block not locked 1: current block locked table 75. extended read single block response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 36. extended read single block frame exchange between vcd and st25dvxxx vcd sof extended read single block request eof st25dvxxx <-t 1 -> sof extended read single block response eof rf operations ST25DV04K st25dv16k st25dv64k 116/220 docid027603 rev 4 during the rf write cycle w t , there should be no modulation (neither 100% nor 10%), otherwise the st25dvxxx may not program correctly the data into the memory. the w t time is equal to t 1nom + n 302 s (n is an integer). block number is coded on 1 byte and only first 256 blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. request parameters: ? request flags ? uid (optional) ? block number ? data response parameter: ? no parameter. the response is sent back after the writing cycle. response parameter: ? error code as error_flag is set (a) : ? 03h: command option not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 12h: the specified block is locked or prot ected and its contents cannot be changed ? 13h: the specified block was not successfully programmed table 76. write single block request format request sof request_flags write single block uid (1) 1. gray color means that the field is optional. block number data crc16 request eof - 8 bits 21h 64 bits 8 bits 32 bits 16 bits - table 77. write single bl ock response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 78. write single block response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - a. for more details, see figure 7: memory organization docid027603 rev 4 117/220 ST25DV04K st25dv16k st25dv64k rf operations 219 7.6.9 extended write single block on receiving the extended write single command, the st25dvxxx writes the data contained in the request to the targeted block and reports whether the write operation was successful in the response. when the option _flag is set, wait for eof to respond. the inventory_flag must be set to 0. during the rf write cycle w t , there should be no modulation (neither 100% nor 10%), otherwise the st25dvxxx may not program correctly the data into the memory. the w t time is equal to t 1nom + n 302 s (n is an integer). block number is coded on 1 byte and only first 256 blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. request parameters: ? request flags ? uid (optional) ? block number ? data response parameter: ? no parameter. the response is sent back after the writing cycle. figure 37. write single block frame exchange between vcd and st25dvxxx vcd sof write single block request eof st25dvxxx <-t 1 -> sof write single block response eof write sequence when error st25dvxxx <------------------- w t ---------------> sof write single block response eof table 79. extended write single request format request sof request_flags extended write single block uid (1) 1. gray color means that the field is optional. block number data crc16 request eof - 8 bits 31h 64 bits 16 bits 32 bits 16 bits - table 80. extended write single respons e format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 118/220 docid027603 rev 4 response parameter: ? error code as error_flag is set: ? 03h: command option not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 12h: the specified block is locked and its contents cannot be changed ? 13h: the specified block was not successfully programmed 7.6.10 lock block on receiving the lock block request, th e st25dvxxx locks the si ngle block value permanently and protects its content against new writing. this command is only applic able for the blocks 0 and 1 which may include a cc file. for a global protection of a area, update accordingly the rfa i ss bits in the system area. the option_flag is supported, when set wait for eof to respond. the inventory_flag must be set to 0. during the rf write cycle w t , there should be no modulation (neither 100% nor 10%), otherwise the st25dvxxx may not lock correctly the single block value in memory. the w t time is equal to t 1nom + n 302 s (n is an integer). table 81. extended write single response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 38. extended write single frame exchange between vcd and st25dvxxx vcd sof extended write single request eof st25dvxxx <-t 1 -> sof extended write single response eof write sequence when error st25dvxxx <------------------- w t ---------------> sof extended write single response eof table 82. lock block request format request sof request_flags lock block uid (1) 1. gray color means that the field is optional. block number cr7c16 request eof - 8 bits 22h 64 bits 8 bits 16 bits - docid027603 rev 4 119/220 ST25DV04K st25dv16k st25dv64k rf operations 219 request parameter: ? request flags ? uid (optional) ? block number (only value 00h or 01h) are allowed to protect the ccfile in case of ndef usage. response parameter: ? no parameter response parameter: ? error code as error_flag is set ? 03h: command option not supported ? 10h: block not available ? 11h: the specified block is already locked and thus cannot be locked again ? 14h: the specified block was not successfully locked table 83. lock block response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 84. lock single block response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 39. lock single block frame exchange between vcd and st25dvxxx vcd sof lock block request eof st25dvxxx <-t 1 -> sof lock block response eof lock sequence when error st25dvxxx <----------------- w t -----------> sof lock block response eof rf operations ST25DV04K st25dv16k st25dv64k 120/220 docid027603 rev 4 7.6.11 extended lock block on receiving the extended lock block reques t, the st25dvxxx locks the single block value permanently and protects its content against new writing. this command is only applic able for the blocks 0 and 1 which may include a cc file. for a global protection of a ar ea, update accordingly the aiss bits in the system area. when the option_flag is set, wait for eof to respond. the inventory_flag must be set to 0. during the rf write cycle w t , there should be no modulation (neither 100% nor 10%), otherwise the st25dvxxx may not lock correctly the single block value in memory. the w t time is equal to t 1nom + n 302 s (n is an integer). request parameter: ? request flags ? uid (optional) ? block number (only value 00h or 01h) are allowed to protect the ccfile in case of ndef usage. response parameter: ? no parameter response parameter: ? error code as error_flag is set ? 03h: command option not supported ? 10h: block not available ? 11h: the specified block is already locked and thus cannot be locked again ? 14h: the specified block was not successfully locked table 85. extended lock block request format request sof request_flags extended lock block uid (1) 1. gray color means that the field is optional. block number crc16 request eof - 8 bits 32h 64 bits 16 bits 16 bits - table 86. extended lock block response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 87. extended lock block response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - docid027603 rev 4 121/220 ST25DV04K st25dv16k st25dv64k rf operations 219 7.6.12 read multiple blocks when receiving the read multiple block command, the st25dvxxx reads the selected blocks and sends back their value in multiple s of 32 bits in the response. the blocks are numbered from 00h to ffh in the request and the value is minus one (?1) in the field. for example, if the ?number of blocks? field cont ains the value 06h, seven blocks are read. the maximum number of blocks is fixed at 256 assuming that they are all located in the same area. if the number of blocks overlaps areas or overlaps the end of user memory, the st25dvxxx returns an error code. when the option_flag is set, the response returns the block security status. the inventory_flag must be set to 0. block number is coded on 1 byte and only first 256 blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. request parameters: ? request flags ? uid (optional) ? first block number ? number of blocks figure 40. extended lock block frame exchange between vcd and st25dvxxx vcd sof extended lock block request eof st25dvxxx <-t 1 -> sof extended lock block response eof lock sequence when error st25dvxxx <----------------- w t -----------> sof extended lock block response eof table 88. read multiple block request format request sof request_ flags read multiple block uid (1) 1. gray color means that the field is optional. first block number number of blocks crc16 request eof -8 bits 23h 64 bits 8 bits 8 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 122/220 docid027603 rev 4 response parameters: ? block security status if option_flag is set (see table 90: block security status ) ? n blocks of data response parameter: ? error code as error_flag is set: ? 03h: command option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 15h: the specified block is read-protected 7.6.13 extended read multiple blocks when receiving the extended read multiple block command, the st25dvxxx reads the selected blocks and sends back their value in multiples of 32 bits in the response. the blocks are numbered from 00h to last block of memory in the request and the value is minus one (-1) in the field. for example, if the ?n umber of blocks? field contains the value 06h, seven blocks are read. the maximum number of blocks is fixed at 2047 assuming that they are all located in the same area. if the number of blocks overlaps areas or overlaps the end table 89. read multiple block response format when error_flag is not set response sof response_ flags block security status (1) 1. gray color means that the field is optional. data crc16 response eof -8 bits 8 bits (2) 2. repeated as needed. 32 bits (2) 16 bits - table 90. block security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use. all at 0. 0: current block not locked 1: current block locked table 91. read multiple block response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 41. read multiple block frame exchange between vcd and st25dvxxx vcd sof read multiple block request eof st25dvxxx <-t 1 -> sof read multiple block response eof docid027603 rev 4 123/220 ST25DV04K st25dv16k st25dv64k rf operations 219 of user memory, the st25dvxxx returns an error code. when the option_flag is set, the response returns the block security status. the inventory_flag must be set to 0. block number is coded on 2 bytes so a ll memory blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. request parameters: ? request flags ? uid (optional) ? first block number ? number of blocks response parameters: ? block security status if option_flag is set (see table 94: block security status ) ? n blocks of data table 92. extended read multiple block request format request sof request_ flags extended read multiple block uid (1) 1. gray color means that the field is optional. first block number number of blocks crc16 request eof -8 bits 33h 64 bits 16 bits 16 bits 16 bits - table 93. extended read multiple block response format when error_flag is not set response sof response_ flags block security status (1) 1. gray color means that the field is optional. data crc16 response eof -8 bits 8 bits (2) 2. repeated as needed. 32 bits (2) 16 bits - table 94. block security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use. all at 0 0: current block not locked 1: current block locked table 95. extended read multiple block response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 124/220 docid027603 rev 4 response parameter: ? error code as error_flag is set: ? 03h: command option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 15h: the specified block is read-protected 7.6.14 write multiple blocks on receiving the write multip le block command, the st25dvxxx writes the data contained in the request to the requested blocks, and reports whether the write operation were successful in the response. st25 dvxxx supports up to 4 blocks, data field must be coherent with the number of blocks to program. if some blocks overlaps areas, or overlap end of user memory, the st25dvxxx returns an error code and none of the blocks are programme d. when the option_flag is set, wait for eof to respond. during the rf write cycle wt, there should be no modulation (neither 100% nor 10%), otherwise the st25dv xxx may not program correctly the data into the memory. the w t time is equal to t 1nom + m 302 s < 20 ms. (m is an integer, it is function of nb number of blocks to be programmed). the inventory_flag must be set to 0. block number is coded on 1 byte and only first 256 blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. figure 42. extended read multiple block frame exchange between vcd and st25dvxxx vcd sof extended read multiple block request eof st25dvxxx <-t 1 -> sof extended read multiple block response eof table 96. write multiple block request format request sof request_flags write multiple block uid (1) first block number number of block (2) data crc16 request eof - 8 bits 24h 64 bits 8 bits 8 bits block length (3) 16 bits - 1. gray color means that the field is optional. 2. the number of blocks in the req uest is one less than the number of blocks that the vicc shall write. 3. repeated as needed docid027603 rev 4 125/220 ST25DV04K st25dv16k st25dv64k rf operations 219 request parameters: ? request flags ? uid (optional) ? first block number ? number of blocks ? data response parameter: ? no parameter. the response is sent back after the writing cycle. response parameter: ? error code as error_flag is set: ? 03h: command option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 12h: the specified block is locked and its contents cannot be changed ? 13h: the specified block was not successfully programmed table 97. write multiple block respon se format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 98. write multiple block resp onse format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 43. write multiple block frame exchange between vcd and st25dvxxx vcd sof write multiple block request eof st25dvxxx <-t 1 -> sof write multiple block response eof write sequence when error st25dvxxx <---------------- m * w t ------------> sof write multiple block response eof rf operations ST25DV04K st25dv16k st25dv64k 126/220 docid027603 rev 4 7.6.15 extended write multiple blocks on receiving the extended writ e multiple block command, th e st25dvxxx writes the data contained in the request to th e targeted blocks and reports whet her the write operation were successful in the response. st25 dvxxx supports up to 4 blocks, data field must be coherent with number of blocks to program. if some blocks overlaps areas, or overlap end of user memory the st25dvxxx returns an error code and none of the blocks are programmed. when the option_flag is set, wa it for eof to respond. during the rf write cycle wt, there should be no modulation (neither 100% nor 10%), otherwise the st25dvxxx may not program correctly the data into the memory. the w t time is equal to t 1nom + m 302 s < 20 ms (m is an integer function of nb number of blocks to be programmed). the inventory_flag must be set to 0. block number is coded on 2 bytes so a ll memory blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. request parameters: ? request flags ? uid (optional) ? first block number ? number of block ? data (from first to last blocks, from lsb bytes to msb bytes) response parameter: ? no parameter. the response is sent back after the writing cycle. table 99. extended write multiple block request format request sof request_flags extended write multiple block uid (1) first block number number of block (2) data crc16 request eof - 8 bits 34h 64 bits 16 bits 16 bits block length (3) 16 bits - 1. gray color means that the field is optional. 2. the number of blocks in the req uest is one less than the number of blocks that the vicc shall write. 3. repeated as needed table 100. extended write multiple block response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - docid027603 rev 4 127/220 ST25DV04K st25dv16k st25dv64k rf operations 219 response parameter: ? error code as error_flag is set: ? 03h: command option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 12h: the specified block is locked and its contents cannot be changed ? 13h: the specified block was not successfully programmed 7.6.16 select when receiving the select command: ? if the uid is equal to its own uid, the st 25dvxxx enters or stays in the selected state and sends a response. ? if the uid does not match its own uid, t he selected st25dvxxx returns to the ready state and does not send a response. the st25dvxxx answers an error code only if the uid is equal to its own uid. if not, no response is generated. if an error occurs, the st25dvxxx remains in its current state. the option_flag is not supported, and the inventory_flag must be set to 0. table 101. extended write multiple block response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 44. extended write multiple block frame exchange between vcd and st25dvxxx vcd sof extended write multiple block request eof st25dvxxx <-t 1 -> sof extended write multiple block response eof write sequence when error st25dvxxx <------------------- w t ---------------> sof extended write multiple block response eof table 102. select request format request sof request_flags select uid crc16 request eof - 8 bits 25h 64 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 128/220 docid027603 rev 4 request parameter: ? uid response parameter: ? no parameter response parameter: ? error code as error_flag is set: ? 03h: the option is not supported ? 0fh: error with no information given 7.6.17 reset to ready on receiving a reset to ready command, the st25dvxxx returns to th e ready state if no error occurs. in the addressed mode, the st25 dvxxx answers an error code only if the uid is equal to its own uid. if not, no response is generated. the option_flag is not supported, and the inventory_flag must be set to 0. table 103. select block response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 104. select response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 45. select frame exchange between vcd and st25dvxxx vcd sof select request eof st25dvxxx <-t 1 -> sof select response eof table 105. reset to ready request format request sof request_flags reset to ready uid (1) 1. gray color means that the field is optional. crc16 request eof - 8 bits 26h 64 bits 16 bits - docid027603 rev 4 129/220 ST25DV04K st25dv16k st25dv64k rf operations 219 request parameter: ? uid (optional) response parameter: ? no parameter response parameter: ? error code as error_flag is set: ? 03h: the option is not supported ? 0fh: error with no information given 7.6.18 write afi on receiving the write afi request, the st25d vxxx programs the 8-bit afi value to its memory. when the option_flag is set, wait for eof to respond. the inventory_flag must be set to 0. during the rf write cycle w t , there should be no modulation (neither 100% nor 10%), otherwise the st25dvxxx may not write correctly the afi value into the memory. the w t time is equal to t 1nom + n 302 s (n is an integer). table 106. reset to ready response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 107. reset to ready response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 46. reset to ready frame exchange between vcd and st25dvxxx vcd sof reset to ready request eof st25dvxxx <-t 1 -> sof reset to ready response eof rf operations ST25DV04K st25dv16k st25dv64k 130/220 docid027603 rev 4 request parameter: ? request flags ? uid (optional) ? afi response parameter: ? no parameter response parameter: ? error code as error_flag is set ? 03h: command option is not supported ? 0fh: error with no information given ? 12h: the specified block is locked and its contents cannot be changed ? 13h: the specified block was not successfully programmed table 108. write afi request format request sof request_flags write afi uid (1) 1. gray color means that the field is optional. afi crc16 request eof - 8 bits 27h 64 bits 8 bits 16 bits - table 109. write afi response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 110. write afi response format when error_flag is set response sof response_ flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 47. write afi frame exchange between vcd and st25dvxxx vcd sof write afi request eof st25dvxxx <-t 1 -> sof write afi response eof write sequence when error st25dvxxx <------------------ w t --------------> sof write afi response eof docid027603 rev 4 131/220 ST25DV04K st25dv16k st25dv64k rf operations 219 7.6.19 lock afi on receiving the lock afi request, the st25dvxxx locks the afi value permanently. when the option_flag is set, wait for eof to respond. the inventory_flag must be set to 0. during the rf write cycle w t , there should be no modulation (neither 100% nor 10%), otherwise the st25dvxxx may not lock corr ectly the afi value in memory. the w t time is equal to t 1nom + n 302 s (n is an integer). request parameter: ? request flags ? uid (optional) response parameter: ? no parameter response parameter: ? error code as error_flag is set ? 03h: command option is not supported ? 0fh: error with no information given ? 11h: the specified block is already locked and thus cannot be locked again ? 14h: the specified block was not successfully locked table 111. lock afi request format request sof request_flag slock afi uid (1) 1. gray color means that the field is optional. crc16 request eof - 8 bits 28h 64 bits 16 bits - table 112. lock afi response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 113. lock afi response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 132/220 docid027603 rev 4 7.6.20 write dsfid on receiving the write dsfid request, the st25dvxxx progra ms the 8-bit dsfid value to its memory. when the option_flag is set, wait for eof to respond. the inventory_flag must be set to 0. during the rf write cycle w t , there should be no modulation (neither 100% nor 10%), otherwise the st25dvxxx may not write corr ectly the dsfid value in memory. the w t time is equal to t 1nom + n 302 s (n is an integer). request parameter: ? request flags ? uid (optional) ? dsfid response parameter: ? no parameter figure 48. lock afi frame exchange between vcd and st25dvxxx vcd sof lock afi request eof st25dvxxx <-t 1 -> sof lock afi response eof lock sequence when error st25dvxxx <----------------- w t -----------> sof lock afi response eof table 114. write dsfid request format request sof request_flags w rite dsfid uid (1) 1. gray color means that the field is optional. dsfid crc16 request eof - 8 bits 29h 64 bits 8 bits 16 bits - table 115. write dsfid response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - docid027603 rev 4 133/220 ST25DV04K st25dv16k st25dv64k rf operations 219 response parameter: ? error code as error_flag is set ? 03h: command option is not supported ? 0fh: error with no information given ? 12h: the specified block is locked and its contents cannot be changed ? 13h: the specified block was not successfully programmed 7.6.21 lock dsfid on receiving the lock dsfid request, the st 25dvxxx locks the dsfid value permanently. when the option_flag is se t, wait for eof to respond. the inventory_flag must be set to 0. during the rf write cycle w t , there should be no modulation (neither 100% nor 10%), otherwise the st25dvxxx may not lock corr ectly the dsfid value in memory. the w t time is equal to t 1nom + n 302 s (n is an integer). request parameter: ? request flags ? uid (optional) table 116. write dsfid response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 49. write dsfid frame exchange between vcd and st25dvxxx vcd sof write dsfid request eo f st25dvxxx <-t 1 -> so f write dsfid response eo f write sequence when error st25dvxxx <---------------- w t ----------> so f write dsfid response eof table 117. lock dsfid request format request sof request_flags lock dsfid uid (1) 1. gray color means that the field is optional. crc16 request eof -8 bits 2ah 64 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 134/220 docid027603 rev 4 response parameter: ? no parameter. response parameter: ? error code as error_flag is set: ? 03h: command option is not supported ? 0fh: error with no information given ? 11h: the specified block is already locked and thus cannot be locked again ? 14h: the specified block was not successfully locked 7.6.22 get system info when receiving the get system info command , the st25dvxxx sends back its information data in the response. the option_flag is not supported. the inventory_ flag must be set to 0. the get system info can be issued in both addressed and non addressed modes. table 118. lock dsfid response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 119. lock dsfid response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 50. lock dsfid frame exchange between vcd and st25dvxxx vcd sof lock dsfid request eof st25dvxxx <-t 1 -> sof lock dsfid response eof lock sequence when error st25dvxxx <---------------- w t -------------> sof lock dsfid response eof docid027603 rev 4 135/220 ST25DV04K st25dv16k st25dv64k rf operations 219 request parameter: ? request flags ? uid (optional) response parameters: ? information flags set to 0bh/ 0fh. dsfid, afi and ic reference fields are present. ? uid code on 64 bits ? dsfid value ? afi value ? memsize: block size in bytes and memory size in number of blocks (only present for ST25DV04K-xx configurations) ? st25dvxxx ic reference: the 8 bits are significant. table 120. get system info request format request sof request_flags get system info uid (1) 1. gray color means that the field is optional. crc16 request eof - 8 bits 2bh 64 bits 16 bits - table 121. get system info response format error_flag is not set device response sof response flags information flags uid dsfid afi mem. size ic ref. crc16 response eof st25dv64k-xx st25dv16k-xx -00h 0bh 64 bits 8 bits 8 bits na (1) 26h 16 bits - ST25DV04K-xx 0fh 037fh 24h 1. field not present in this configuration table 122. memory size msb lsb 16 14 13 9 8 1 rfu block size in byte number of blocks 0h 03h 7fh table 123. get system info response format when error_flag is set response sof response_flags error code crc16 response eof - 01h 8 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 136/220 docid027603 rev 4 response parameter: ? error code as error_flag is set: ? 03h: option not supported ? 0fh: error with no information given . 7.6.23 extended get system info when receiving the extended get system info command, the st25dvxxx sends back its information data in the response. the option_flag is not supported. the inventory_flag must be set to 0. the extended get system info can be issued in both addressed and non addressed modes. ? request flags ? request parameters ? uid (optional) m figure 51. get system info frame exchange between vcd and st25dvxxx vcd sof get system info request eof st25dvxxx <-t 1 -> sof get system info response eof table 124. extended get system info request format request sof request_flags extended get system info parameter request field uid (1) 1. gray color means that the field is optional. crc16 request eof - 8 bits 3bh 8 bits 64 bits 16 bits - table 125. parameter request list bit flag name value description b1 dsfid 0 no request of dsfid 1 request of dsfid b2 afi 0 no request of afi 1 request of afi b3 vicc memory size 0 no request of data field on vicc memory size 1 request of data field on vicc memory size b4 ic reference 0 no request of information on ic reference 1 request of information on ic reference b5 moi 1 information on moi always returned in response flag docid027603 rev 4 137/220 ST25DV04K st25dv16k st25dv64k rf operations 219 response parameters: ? information flag defining which fields are present ? uid code on 64 bits ? dsfid value (if requested in parameters request field) ? afi value (if requested in parameters request field) ? other fields: ? vicc memory size (if requeste d in parameters request field) ? icref (if requested in parameters request field) ? vicc command list (if requested in parameters request field) b6 vicc command list 0 no request of data field of all supported commands 1 request of data field of all supported commands b7 csi information 0 no request of csi list 1 request of csi list b8 extended get system info parameter field 0 one byte length of extended get system info parameter field table 125. parameter request list (continued) bit flag name value description table 126. extended get system info response format when error_flag is not set response sof response_flag s information flags uid dsfid (1)(2) afi (1)(2) other field (1)(2) crc16 response eof - 00h 8 bits (2) 64 bits 8 bits 8 bits up to 64 bits (3) 16 bits - 1. gray color means that the field is optional. 2. see table 127: response information flag . 3. number of bytes is function of parameter list selected. table 127. response information flag bit flag name value description b1 dsfid 0 dsfid field is not present 1 dsfid field is present b2 afi 0 afi field is not present 1 afi field is present b3 vicc memory size 0 data field on vicc memory size is not present. 1 data field on vicc memory size is present. b4 ic reference 0 information on ic reference field is not present. 1 information on ic reference field is present. rf operations ST25DV04K st25dv16k st25dv64k 138/220 docid027603 rev 4 b5 moi 0 1 byte addressing 1 2 byte addressing b6 vicc command list 0 data field of all supported commands is not present 1 data field of all supported commands is present b7 csi information 0 csi list is not present b8 info flag field 0 one byte length of info flag field table 128. response other field: st25dvxxx vicc memory size msb lsb 24 22 21 17 16 01 rfu block size in byte number of blocks 0h 03h 07ffh (st25dv64k-xx) 01ffh (st25dv16k-xx) 007fh (ST25DV04K-xx) table 129. response other field: st25dvxxx ic ref 1 byte icref 24h (ST25DV04K-xx) or 26h (st25dv16k-xx and st25dv64k-xx) table 130. response other field: st25dvxxx vicc command list msb lsb 32 25 24 17 16 09 08 01 byte 4 byte3 byte 2 byte 1 00h 3fh 3fh ffh table 131. response other field: st25dvxxx vicc command list byte 1 bit meaning if bit is set comment b1 read single block is supported - b2 write single block is supported - b3 lock single block is supported - table 127. response information flag (continued) bit flag name value description docid027603 rev 4 139/220 ST25DV04K st25dv16k st25dv64k rf operations 219 b4 read multiple block is supported - b5 write multiple block is supported - b6 select is supported including select state b7 reset to ready is supported - b8 get multiple block security status is supported - table 132. response other field: st25dvxxx vicc command list byte 2 bit meaning if bit is set comment b1 write afi is supported - b2 lock afi is supported - b3 write dsfid is supported - b4 lock dsfid is supported - b5 get system information is supported - b6 custom commands are supported - b7 rfu 0 shall be returned b8 rfu 0 shall be returned table 133. response other field: st25dvxxx vicc command list byte 3 bit meaning if bit is set comment b1 extended read single block is supported - b2 extended write single block is supported - b3 extended lock single block is supported - b4 extended read multiple block is supported - b5 extended write multiple block is supported - b6 extended get multiple security status is supported - b7 rfu 0 shall be returned b8 rfu 0 shall be returned table 131. response other field: st25dvxx x vicc command list byte 1 (continued) bit meaning if bit is set comment rf operations ST25DV04K st25dv16k st25dv64k 140/220 docid027603 rev 4 response parameter: ? error code as error_flag is set: ? 03h: option not supported ? 0fh: error with no information given . 7.6.24 get multiple block security status when receiving the get multiple block secu rity status command, the st25dvxxx sends back its security status for each address block: 0 when block is writable else 1 when block is locked for writing. the blocks security status ar e defined by the area security status (and by lck_ccfile register for blocks 0 and 1). the blocks are numbered from 00h up to the maximum memory block number in the request, and the value is minus one (?1) in the field. for example, a value of ?06? in the ?number of blocks? field requests will return the security status of seven blocks. this command does not respond an error if number of blocks overlap areas or overlap the end of the user memory. table 134. response other field: st25dvxxx vicc command list byte 4 bit meaning if bit is set comment b1 read buffer is supported means response buffer is supported b2 select secure state is supported means vcd or mutual authentication are supported b3 final response always includes crypto result means that flag b3 will be set in the final response b4 authcomm crypto format is supported - b5 securecomm crypto format is supported - b6 keyupdate is supported - b7 challenge is supported - b8 if set to 1 a further byte is transmitted 0 shall be returned table 135. extended get system info response format when error_flag is set response sof response_flags error code crc16 response eof - 01h 8 bits 16 bits - figure 52. extended get system info frame exchange between vcd and st25dvxxx vcd sof extended get system info request eof st25dvxxx <-t 1 -> sof extended get system info response eof docid027603 rev 4 141/220 ST25DV04K st25dv16k st25dv64k rf operations 219 the number of blocks is coded on 1 byte and only first 256 blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. the option_flag is not supported. the inventory_flag must be set to 0. request parameter: ? request flags ? uid (optional) ? first block number ? number of blocks response parameters: ? block security status response parameter: ? error code as error_flag is set: ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available table 136. get multiple block security status request format request sof request _flags get multiple block security status uid (1) 1. gray color means that the field is optional. first block number number of blocks crc16 request eof -8 bits 2ch 64 bits 8 bits 8 bits 16 bits - table 137. get multiple block security status response format when error_flag is not set response sof response_flags block security status crc16 response eof - 8 bits 8 bits (1) 1. repeated as needed. 16 bits - table 138. block security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use all at 0 0: current block not locked 1: current block locked table 139. get multiple block security status response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 142/220 docid027603 rev 4 7.6.25 extended get multip le block security status when receiving the extended get multiple block security status command, the st25dvxxx sends back the security status for each address block: 0 when the block is writable else 1 when block is locked for writing. the block security statuses ar e defined by the area security status. the blocks are numbered from 00h up to the maximum memory block number in the request, and the value is minus one (?1) in t he field. for example, a value of '06' in the ?number of blocks? field requests to return the security status of seven blocks. this command does not respond an error if number of blocks overlap areas or overlap the end of the user memory. the number of blocks is coded on 2 bytes so all memory blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. the option_flag is not supported. the inventory_flag must be set to 0. request parameter: ? request flags ? uid (optional) ? first block number ? number of blocks figure 53. get multiple block security status frame exchange between vcd and st25dvxxx vcd sof get multiple block security request status eof st25dvxxx <-t 1 -> sof get multiple block security response status eof table 140. extended get multiple block security status request format request sof request _flags extended get multiple block security status uid (1) 1. gray color means that the field is optional. first block number number of blocks crc16 request eof -8 bits 3ch 64 bits 16 bits 16 bits 16 bits - table 141. extended get multiple block security status response format when error_flags not set response sof response_flags block security status crc16 response eof - 8 bits 8 bits (1) 1. repeated as needed. 16 bits - docid027603 rev 4 143/220 ST25DV04K st25dv16k st25dv64k rf operations 219 response parameters: ? block security status response parameter: ? error code as error_flag is set: ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: the specified block is not available 7.6.26 read configuration on receiving the read configuration comma nd, the st25dvxxx reads the static system configuration register at the pointer address and sends back its 8-bit value in the response. the option_flag is not supported. the inventory_flag must be set to 0. table 142. block security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use all at 0 0: current block not locked 1: current block locked table 143. extended get multiple block security status response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 54. extended get multiple block security status frame exchange between vcd and st25dvxxx vcd sof extended get multiple block security request status eof st25dvxxx <-t 1 -> sof extended get multiple block security reply status eof table 144. read configuration request format request sof request_flags read configuration ic mfg code uid (1) pointer crc16 request eof - 8 bits a0h 02h 64 bits 8 bits 16 bits - 1. gray color means that the field is optional. rf operations ST25DV04K st25dv16k st25dv64k 144/220 docid027603 rev 4 note: please refer to table 8: system configuration memory map for details on register addresses. request parameters: ? system configuration register pointer ? uid (optional) response parameters: ? one byte of data: system configuration register response parameter: ? error code as error_flag is set ? 02h: command not recognized ? 03h: the option is not supported ? 10h: block not available ? 0fh: error with no information given figure 55. read configuration frame exchange between vcd and st25dvxxx 7.6.27 write configuration the write configuration command is used to wr ite static system configuration register. the write configuration must be preceded by a valid presentation of the rf configuration password (00) to open the rf configuration security session. on receiving the write configuration command, the st25dvxxx writes the data contained in the request to the system confi guration register at the pointe r address and re ports whether the write operation was successful in the response or not. when the option_flag is set, wa it for eof to respond. the inventory_flag is not supported. table 145. read configuration response format when error_flag is not set response sof response_flags register value crc16 response eof - 8 bits 8 bits 16 bits - table 146. read configuration response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - vcd sof read configuration request eof st25dvxxx <-t 1 -> sof read configuration response eof docid027603 rev 4 145/220 ST25DV04K st25dv16k st25dv64k rf operations 219 during the rf write cycle w t , there should be no modulation (neither 100% nor 10%), otherwise the st25dvxxx may not program correctly the data into the configuration byte. the w t time is equal to t 1nom + n 302 s (n is an integer). request parameters: ? request flags ? register pointer ? register value ? uid (optional) note: please refer to table 8: system configuration memory map for details on register addresses. response parameter: ? no parameter. the response is sent back after the writing cycle. response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: command option is not supported ? 0fh: error with no information given ? 10h: block not available ? 12h: block already locked, content can't change ? 13h: the specified block was not successfully programmed table 147. write configuration request format request sof request_ flags write configuration ic mfg code uid (1) pointer register value (2) crc16 request eof - 8 bits a1h 02h 64 bits 8 bits 8 bits 16 bits - 1. gray color means that the field is optional. 2. before updating the register value, check the meaning of each bit in previous sections. table 148. write configuration response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 149. write configuration response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 146/220 docid027603 rev 4 7.6.28 read dynamic configuration on receiving the read dynamic confi guration command, the st25dvxxx reads the dynamic register address indicated by the pointer and sends back its 8-bit value in the response. the option_flag is not supported. the inventory_flag must be set to 0. request parameters: ? uid (optional) response parameters: ? one byte of data note: please refer to table 8: system configuration memory map for details on register addresses. figure 56. write configuration frame exchange between vcd and st25dvxxx vcd sof write configuration request eof st25dvxxx <-t 1 -> sof write configuration response eof write configuration sequence when error st25dvxxx <------------------- w t ---------------> sof write configuration response eof table 150. read dynamic configuration request format request sof request_flags read dynamic configuration ic mfg code uid (1) pointer address crc16 request eof - 8 bits adh 02h 64 bits 8 bits 16 bits - 1. gray color means that the field is optional. table 151. read dynamic configuration response format when error_flag is not set response sof response_flags data crc16 response eof - 8 bits 8 bits 16 bits - docid027603 rev 4 147/220 ST25DV04K st25dv16k st25dv64k rf operations 219 response parameter: ? error code as error_flag is set ? 02h: command not recognized ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: block not available 7.6.29 write dynamic configuration on receiving the write dynamic configur ation command, the st25dvxxx updates the dynamic register addressed by the pointer. the option_flag is not supported. the inventory_flag must be set to 0. request parameters: ? request flags ? uid (optional) ? pointer address ? register value table 152. read dynamic configuration response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 57. read dynamic configuration frame exchange between vcd and st25dvxxx vcd sof read dynamic configuration request eof st25dvxxx <-t 1 -> sof read dynamic configuration response eof table 153. write dynamic configuration request format request sof request_flags write dynamic configuration ic mfg code uid (1) pointer address register value crc16 request eof - 8 bits aeh 02h 64 bits 8 bits 8 bits 16 bits - 1. gray color means that the field is optional. rf operations ST25DV04K st25dv16k st25dv64k 148/220 docid027603 rev 4 response parameter: ? no parameter. the response is sent back after t 1 . response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: block not available 7.6.30 manage gpo on receiving the manage gpo command. depending on the command argument, the st25dv force the gpo output le vel if rf_user interrupt is enabled, or send a pulse on gpo output if rf_interrupt is enabled. if neither rf_user no r rf_interrupt was enabled, the command is not executed and st25dvxxx responds an error code ?0f?. the it duration is defined by it_time register and occurs just after the command response. for the st25dvxx-jf (cmos output), a set me ans that the gpo pin is driven to a high level (v dcg ) and a reset pulls the gpo pin to a low level (v ss ). the it corresponds to a transmission of a positive pulse on the gpo pin. table 154. write dynamic configuration resp onse format when erro r_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 155. write dynamic configuration response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 58. write dynamic configuration frame exchange between vcd and st25dvxxx vcd sof write dynamic configuration request eo f st25dvxxx <-t 1 -> sof write dynamic configuration response eof write dynamic configuration sequence when no error st25dvxxx <-t 1 -> sof write dynamic configuration response eof write dynamic configuration sequence when error docid027603 rev 4 149/220 ST25DV04K st25dv16k st25dv64k rf operations 219 for the st25dvxx-ie (open drain output), a set means that the gpo pin is driven to a low level (v ss ) and a reset releases the gpo (high impedance). it corresponds to the gpo pin driven to ground during the it duration, then pin is released. thanks to an external pull up, the high level will be recovered. option_flag is not supported. the inventory_flag must be set to 0. request parameters: ? request flag ? uid (optional) ? data: define static or dynamic interrupt response parameter: ? no parameter. the response is sent back after the write cycle. table 156. managegpo request format request sof request_ flags managegpo ic mfg code uid (1) 1. gray color means that the field is optional. gpo val (2) 2. see table 157: gpoval crc16 request eof - 8 bits a9h 02h 64 bits 8 bits 16 bits - table 157. gpoval gpoval it st25dvxx-ie (od) st25dvxx-jf (cmos) 0xxxxxx0b rf_user enabled pin pull to 0 gpo pin set to logic one (v dcg ) 0xxxxxx1b rf_user enabled pin released (hz) gpo pin reset to logic zero 1xxxxxxxb rf_interrupt enabled gpo pin pulled to 0 during it time then released (hz) gpo pin drives a positive pulse any other conditions gpo realeased (hz) gpo pin reset to logic zero table 158. managegpo response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 159. managegpo response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 150/220 docid027603 rev 4 response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 13h: the specified block was not successfu lly programmed (this error is generated if the managecpo gpoval value is not in line with the gpo inte rrupts setting as specified in table 157 ) 7.6.31 write message on receiving the write message command, the st25dvxxx puts the data contained in the request into the mailbox buffer, update the mb_len_dyn register, and set bit rf_put_msg in mb_ctrl_dyn register. it then reports if the write operation was successful in the response. the st25dvxxx mailbox contains up to 256 data bytes which are filled from the first location '00'. msglengt h parameter of the command is the number of data bytes minus - 1 (00 for 1 byte of data, ffh for 256 bytes of data). write message could be executed only when mailbox is accessible by rf (fast transfer mode is enabled, previous rf message was read or time-out occurs, no i 2 c message to be read). user can check it by reading b1 of mb_ctrl_dyn ?host_put_ms g? which must be reset to ?0?. the option_flag is not supported. (refer to section 5.1: fast transfer mode (ftm) ) request parameters: ? request flags ? uid (optional) ? message length ? message data figure 59. managegpo frame exchange between vcd and st25dvxxx vcd sof managegpo eof st25dvxxx <-t 1 -> sof managegpo response eof managegpo sequence when error table 160. write message request format request sof request_ flags write message ic mfg code uid (1) msglength message data crc16 request eof - 8 bits aah 02h 64 bits 1 byte (msglength + 1) bytes 16 bits - 1. gray color means that the field is optional. table 161. write message response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - docid027603 rev 4 151/220 ST25DV04K st25dv16k st25dv64k rf operations 219 response parameter: ? no parameter. the response is sent back after the write cycle. response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: command option not supported ? 0fh: error with no information given 7.6.32 read message length on receiving the read message length command, the st25dvxxx reads the mb_len_dyn register which contains the mailbox message length and sends back its 8-bit value in the response. the option_flag is not supported. the inventory_flag must be set to 0. request parameters: ? uid (optional) table 162. write message response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 60. write message frame exchange between vcd and st25dvxxx vcd sof write message request eof st25dvxxx <-t 1 -> sof write message response eof write sequence when error st25dvxxx <------------------- t 1 ---------------> sof write message response eof table 163. read message length request format request sof request_flags read message length ic mfg code uid (1) 1. gray color means that the field is optional. crc16 request eof - 8 bits abh 02h 64 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 152/220 docid027603 rev 4 response parameters: ? one byte of data: mb_len_dyn register value response parameter: ? error code as error_flag is set ? 02h: command not recognized ? 03h: the option is not supported ? 0fh: error given with no information 7.6.33 read message on receiving the read message comma nd, the st25dvxxx reads up to 256 byte in the mailbox from the location specified by mbpointer and sends back their value in the response. first mailbox location is '00?. when number of bytes is set to 00h and mbpointer is equals to 00h, the mb_len bytes of the full message are returned. otherwise, read message command returns (number of bytes + 1) bytes (i.e. 01h returns 2 bytes, ffh returns 256 bytes). an error is reported if (pointer + nb of byte s + 1) is greater than the message length. rf reading of the last byte of the mailbox messa ge automatically clears b1 of mb_ctrl_dyn ?host_put_msg?, and allows rf to put a new message. the option_flag is not supported. the inventory_flag must be set to 0. table 164. read message length response format when error_flag is not set response sof response_flags data crc16 response eof - 8 bits 8 bits 16 bits - table 165. read message length response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 61. read message length frame exchange between vcd and st25dvxxx vcd sof read message length request eof st25dvxxx <-t 1 -> sof read message length response eof docid027603 rev 4 153/220 ST25DV04K st25dv16k st25dv64k rf operations 219 request parameters: ? request flag ? uid (optional) ? pointer (start at 00h) ? number of bytes is one less then the requested data response parameters: ? (number of data + 1 ) data bytes response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: command option not supported ? 0fh: error with no information given 7.6.34 fast read message on receiving the fast read message command, the st25dvxxx reads up to 256 byte in the mailbox from the location specified by mbpointer and sends back their value in the response. first mailbox location is '00?. when number of bytes is set to 00h and mbpointer is equals to 00h, the mb_len bytes of the full message are returned. otherwise, fast read message command returns (number of bytes + 1) bytes (i.e. 01h returns 2 bytes, ffh returns 256 bytes). an error is reported if (pointer + nb of by tes + 1) is greater than the message length.. table 166. read message request format request sof request_ flags read message ic mfg code uid (1) 1. gray color means that the field is optional. mbpointer number of bytes crc16 request eof - 8 bits ach 02h 64 bits 8 bits 8 bits 16 bits - table 167. read message response format when error_flag is not set response sof response_flags mailbox content crc16 response eof - 8 bits (number of bytes + 1) bytes (1) 1. number of message bytes when number of bytes is set to 00h. 16 bits - figure 62. read message frame exchange between vcd and st25dvxxx vcd sof read message request eof st25dvxxx <-t 1 -> sof read message response eof rf operations ST25DV04K st25dv16k st25dv64k 154/220 docid027603 rev 4 rf reading of the last byte of mailbox message automatically clears b1 of mb_ctrl_dyn ?host_put_msg? and allows rf to put a new message. the data rate of the response is multiplied by 2 compated to read message. the subcarrier_flag should be set to 0, otherwise the st25dvxxx answers with an error code. the option_flag is not supported, and the inventory_flag must be set to 0. request parameters: ? request flag ? uid (optional) ? pointer (start at 00h) ? number of bytes is one less than the requested data response parameters: ? (number of bytes + 1) data bytes response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: command option not supported ? 0fh: error with no information given 7.6.35 write password on receiving the write password command, the st25dvxxx uses the data contained in the request to write the password and reports w hether the operation was successful in the response. it is possible to modify a passwo rd value only after issuing a valid present password command (of the same password number). when the option_flag is set, wait for eof to respond. refer to section 5.6: data protection for details on password management. the inventory_flag must be set to 0. during the rf write cycle time, w t , there must be no modulation at all (neither 100% nor 10%), otherwise the st25dvxxx may not correc tly program the data into the memory. the w t time is equal to t 1nom + n 302 s (n is an integer). after a successful write, the new value of the selected password is automatically activated. it is not required to present the new password value until the st25dvxxx power-down. caution: if st25dvxxx is powered through v cc , removing v cc or setting lpd high during write password command can abort the command. as a consequence, before writing a new password, rf user should check if v cc is on, by reading eh_ctrl_dyn register bit 3 (vcc_on), and eventually ask host to maintain or to shut down v cc , and not to change figure 63. fast read message frame exchange between vcd and st25dvxxx vcd sof fast read message request eof st25dvxxx <-t 1 -> sof fast read message response eof docid027603 rev 4 155/220 ST25DV04K st25dv16k st25dv64k rf operations 219 voltage applied on lpd while issuing the write password command in order to avoid password corruption. request parameter: ? request flags ? uid (optional) ? password number: ? 00h = rf configuration password rf_pwd_0, ? 01h = rf_pwd_1, ? 02h = rf_pwd_2, ? 03h = rf_pwd_3, ? other = error) ? data response parameter: ? no parameter. response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: command option not supported ? 10h: the password number is incorrect ? 12h: update right not granted, present password command not previously executed successfully ? 13h: the specified block was not successfully programmed table 168. write password request format request sof request _flags write password ic mfg code uid (1) 1. gray color means that the field is optional. password number data crc16 request eof -8 bits b1h02h 64 bits 8 bits 64 bits 16 bits - table 169. write password response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 170. write password response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 156/220 docid027603 rev 4 7.6.36 present password on receiving the present password command, the st25dvxxx compares the requested password with the data contained in the requ est and reports if the operation has been successful in the response. refer to section 5.6: data protection for details on password management. after a successful command, the se curity session associate to the password is open as described in section 5.6: data protection . the option_flag is not supported, and the inventory_flag must be set to 0. request parameter: ? request flags ? uid (optional) ? password number (00h = password configuration, 0x01 = pswd1, 0x02 = pswd2, 0x03 = pswd3, other = error) ? password response parameter: ? no parameter. the response is sent back after the write cycle. figure 64. write password frame exchange between vcd and st25dvxxx vcd sof write password request eof st25dvxxx <-t 1 -> sof write password response eof write sequence when error st25dvxxx <---------------- w t -------------> sof write password response eof table 171. present password request format request sof request _flags present password ic mfg code uid (1) 1. gray color means that the field is optional. password number password crc16 request eof -8 bitsb3h02h 64 bits 8 bits 64 bits 16 bits - table 172. present password response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - docid027603 rev 4 157/220 ST25DV04K st25dv16k st25dv64k rf operations 219 response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: command option not supported ? 0fh: the present password is incorrect ? 10h: the password number is incorrect 7.6.37 fast read single block on receiving the fast read single blo ck command, the st25dvxxx reads the requested block and sends back its 32-bit value in the response. when the option_flag is set, the response includes the block security status. t he data rate of the response is multiplied by 2. the subcarrier_flag should be set to 0, otherwise the st25dvxxx answers with an error code. the inventory_flag must be set to 0. block number is coded on 1 byte and only first 256 blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. table 173. present password response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 65. present password frame exchange between vcd and st25dvxxx vcd sof present password request eof st25dvxxx <-t 1 -> sof present password response eof table 174. fast read single block request format request sof request_flags fast read single block ic mfg code uid (1) 1. gray color means that the field is optional. block number crc16 request eof -8 bits c0h02h 64 bits 8 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 158/220 docid027603 rev 4 request parameters: ? request flags ? uid (optional) ? block number response parameters: ? block security status if option_flag is set (see table 176: block security status ) ? four bytes of block data response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: command option not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 15h: the specified block is read-protected table 175. fast read single block response format when error_flag is not set response sof response_flags block security status (1) 1. gray color means that the field is optional. data crc16 response eof -8 bits 8 bits 32 bits 16 bits - table 176. block security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use all at 0 0: current block not locked 1: current block locked table 177. fast read single block response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 66. fast read single block frame exchange between vcd and st25dvxxx vcd sof fast read single block request eof st25dvxxx <-t 1 -> sof fast read single block response eof docid027603 rev 4 159/220 ST25DV04K st25dv16k st25dv64k rf operations 219 7.6.38 fast extende d read single block on receiving the fast extended read single block command, the st25dvxxx reads the requested block and sends back its 32-bit va lue in the response. when the option_flag is set, the response includes the block security status. the data rate of the response is multiplied by 2. the subcarrier_flag should be set to 0, otherwise the st25dvxxx answers with an error code. the inventory_flag must be set to 0. block number is coded on 2 bytes so a ll memory blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command request parameters: ? request flags ? uid (optional) ? block number response parameters: ? block security status if option_flag is set (see table 176: block security status ) ? four bytes of block data table 178. fast extended read single block request format request sof request_flags fast extended read single block ic mfg code uid (1) 1. gray color means that the field is optional. block number crc16 request eof -8 bits c4h02h 64 bits 16 bits 16 bits - table 179. fast extended read single block response format when error_flag is not set response sof response_flags block security status (1) 1. gray color means that the field is optional. data crc16 response eof -8 bits 8 bits 32 bits 16 bits - table 180. block security status b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use all at 0 0: current block not locked 1: current block locked rf operations ST25DV04K st25dv16k st25dv64k 160/220 docid027603 rev 4 response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: command option not supported ? 0fh: error with no information given ? 10h: the specified block is not available ? 15h: the specified block is read-protected 7.6.39 fast read multiple blocks on receiving the fast read multiple blocks command, the st25dvxxx reads the selected blocks and sends back their value in multiple s of 32 bits in the response. the blocks are numbered from 00h up to the last block of us er memory in the request, and the value is minus one (?1) in the field. for example, if the ?number of blocks? field contains the value 06h, seven blocks are read. the maximum number of blocks is fixed to 256 assuming that they are all located in the same area. if the number of blocks overlaps area or overlaps the end of user memory, the st25 dvxxx returns an error code. when the option_flag is set, the response incl udes the block security status. the data rate of the response is multiplied by 2. the subcarrier_flag should be set to 0, otherwise the st25dvxxx answers with an error code. the inventory_flag must be set to 0. block number is coded on 1 byte and only first 256 blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. table 181. fast extended read single block response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 67. fast extended read single block frame exchange between vcd and st25dvxxx vcd sof fast extended read single block request eof st25dvxxx <-t 1 -> sof fast extended read single block response eof docid027603 rev 4 161/220 ST25DV04K st25dv16k st25dv64k rf operations 219 request parameters: ? request flag ? uid (optional) ? first block number ? number of blocks response parameters: ? block security status if option_flag is set (see table 184: block security status if option_flag is set ) ? n block of data response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 0fh: error with no information given ? 03h: the option is not supported ? 10h: block address not available ? 15h: block read-protected table 182. fast read multiple block request format request sof request_ flags fast read multiple block ic mfg code uid (1) 1. gray color means that the field is optional. first block number number of blocks crc16 request eof -8 bits c3h02h 64 bits 8 bits 8 bits 16 bits - table 183. fast read mult iple block response format when error_flag is not set response sof response_flags block security status (1) 1. gray color means that the field is optional. data crc16 response eof -8 bits 8 bits (2) 2. repeated as needed. 32 bits (2) 16 bits - table 184. block security status if option_flag is set b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use all at 0 0: current not locked 1: current locked table 185. fast read mult iple block response format when error_flag is set response sof response_flags e rror code crc16 response eof - 8 bits 8 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 162/220 docid027603 rev 4 7.6.40 fast extended read multiple block on receiving the fast extended read multip le block command, th e st25dvxxx reads the selected blocks and sends back their value in multiples of 32 bits in the response. the blocks are numbered from 00h to up to the last block of memory in the request and the value is minus one (?1) in the field. for example, if the ?number of blocks? field contains the value 06h, seven blocks are read. th e maximum number of blocks is fixed to 2047 assuming that they are all located in the same area. if the number of blocks overlaps several areas or overlaps the end of user memory, the st25dvxxx returns an error code. when the option_flag is set, the response incl udes the block security status. the data rate of the response is multiplied by 2. the subcarrier_flag should be set to 0, otherwise the st25dvxxx answers with an error code. the inventory_flag must be set to 0. block number is coded on 2 bytes so a ll memory blocks of st25dv16k-xx and st25dv64k-xx can be addressed using this command. request parameters: ? request flag ? uid (optional) ? first block number ? number of blocks figure 68. fast read multiple block frame exchange between vcd and st25dvxxx vcd sof fast read multiple block request eof st25dvxxx <-t 1 -> sof fast read multiple block response eof table 186. fast extended read multiple block request format request sof request_ flags fast extended read multiple block ic mfg code uid (1) 1. gray color means that the field is optional. first block number block number crc16 request eof -8 bits c5h 02h 64 bits 16 bits 16 bits 16 bits - docid027603 rev 4 163/220 ST25DV04K st25dv16k st25dv64k rf operations 219 response parameters: ? block security status if option_flag is set (see table 184: block security status if option_flag is set ) ? n block of data response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: the option is not supported ? 0fh: error with no information given ? 10h: block address not available ? 15h: block read-protected table 187. fast extended read multiple block response format when error_flag is not set response sof response_flags block security status (1) 1. gray color means that the field is optional. data crc16 response eof -8 bits 8 bits (2) 2. repeated as needed. 32 bits (2) 16 bits - table 188. block security status if option_flag is set b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 reserved for future use all at 0 0: current not locked 1: current locked table 189. fast read mult iple block response format when error_flag is set response sof response_flags e rror code crc16 response eof - 8 bits 8 bits 16 bits - figure 69. fast extended read multiple block frame exchange between vcd and st25dvxxx vcd sof fast extended read multiple block request eof st25dvxxx <-t 1 -> sof fast extended read multiple block response eof rf operations ST25DV04K st25dv16k st25dv64k 164/220 docid027603 rev 4 7.6.41 fast write message on receiving the fast write message command, the st25dvxxx puts the data contained in the request into the mailbox buffer, updates the message length register mb_len_dyn, and set mailbox loaded bit rf_put_msg. it then reports if the write operation was successful in the response. the st25dvxxx mailbox contains up to 256 data bytes which are filled from the first location '00'. msglengt h parameter of the command is the number of data bytes minus - 1 (00 for 1 byte of data, ffh for 256 bytes of data). fast write message can be executed only when mailbox is accessi ble by rf (previous rf message was read or time-out occurs, no i 2 c message to be read). user can check it by reading b1 of mb_ctrl_dyn ?host_put_msg?, which must be reset to ?0?. (refer to section 5.1: fast transfer mode (ftm) ). ? the data rate of the response is multiplied by 2 compared to write message command. ? the option_flag is not supported. ? the inventory_flag must be set to 0. ? the subcarrier_flag should be set to 0, otherwise the st25dvxxx answers with an error code. request parameters: ? request flag ? uid (optional) ? message lenght ? message data response parameters: ? no parameter. the response is sent back after the write cycle. table 190. fast write message request format request sof request _flags fast write message ic mfg code uid (1) msglength message data crc16 request eof - 8 bits cah 02h 64 bits 1 byte (msglenght + 1) bytes 16 bits - 1. gray color means that the field is optional. table 191. fast write message response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 192. fast write message response format when error_flag is set response sof response_flags crc16 response eof - 8 bits 8 bits 16 bits docid027603 rev 4 165/220 ST25DV04K st25dv16k st25dv64k rf operations 219 response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: command option not supported ? 0fh: error with no information given 7.6.42 fast read message length on receiving the fast read message length command, the st25dv reads the mb_len_dyn register which contains the mailbox message length and sends back its 8-bit value in the response. the option_flag is not supported. the inventory_flag must be set to 0. the subcarrier_flag should be set to 0, otherwise the st25dvxxx answers with an error code. the data rate of the response is multiplied by 2 compared to read message length command. request parameters: ? request flag ? uid (optional) figure 70. fast write message frame exchange between vcd and st25dvxxx vcd sof fast write message request eof st25dvxxx <-t 1 -> sof fast write message rresponse0 eof write sequence when error st25dvxxx <------------------- t 1 ---------------> sof fast write message r response eof table 193. fast read message length request format request sof request_flags fast read message length ic mfg code uid (1) 1. gray color means that the field is optional. crc16 request eof - 8 bits cbh 02h 64 bits 16 bits - rf operations ST25DV04K st25dv16k st25dv64k 166/220 docid027603 rev 4 response parameters: ? one byte of data: volatile control register. response parameter: ? error code as error_flag is set: ? 02h: command option not recognized ? 03h: command not supported ? 0fh: error with no information given 7.6.43 fast read dy namic configuration on receiving the fast read dynamic conf iguration command, the st25dvxxx reads the dynamic register address by the pointer and sends back its 8-bit value in the response. the option_flag is not supported. the inventory_flag must be set to 0. the subcarrier_flag should be set to 0, otherwise the st25dvxxx answers with an error code. the data rate of the response is multiplied by 2 compared to read dynamic configuration command. table 194. fast read message length response format when error_flag is not set response sof response_flags data crc16 response eof - 8 bits 8 bits 16 bits - table 195. fast read message length response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 71. fast read message length frame exchange between vcd and st25dvxxx vcd sof fast read message length request eof st25dvxxx <-t 1 -> sof fast read message length request eof table 196. fast read dynamic configuration request format request sof request_flags fast read dynamic configuration ic mfg code uid (1) pointer address crc16 request eof - 8 bits cdh 02h 64 bits 8 bits 16 bits - 1. gray color means that the field is optional. docid027603 rev 4 167/220 ST25DV04K st25dv16k st25dv64k rf operations 219 request parameters: ? request flag ? uid (optional) response parameters: ? one byte of data response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: command option not supported ? 0fh: error with no information given ? 10h: block not available 7.6.44 fast write dy namic configuration on receiving the fast write dynamic conf iguration command, the st25dv updates the dynamic register addressed by the pointer. the option_flag is not supported. the inventory_flag must be set to 0. the data rate of the response is multiplied by 2 compared to write dynamic configuration command. table 197. fast read dynamic configuration response format when error_flag is not set response sof response_flags data crc16 response eof - 8 bits 8 bits 16 bits - table 198. fast read dynamic configuration response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 72. fast read dynamic configuration frame exchange between vcd and st25dvxxx vcd sof fast read dynamic configuration request eof st25dvxxx <-t 1 -> sof fast read dynamic configuration request eof rf operations ST25DV04K st25dv16k st25dv64k 168/220 docid027603 rev 4 request parameters: ? request flag ? uid (optional) ? pointer address ? register value response parameters: ? no parameter. the response is sent back after t 1 . response parameter: ? error code as error_flag is set: ? 02h: command not recognized ? 03h: command option not supported ? 0fh: error with no information given ? 10h: block not available table 199. fast write dynamic configuration request format request sof request_flags fast write dynamic configuration ic mfg code uid (1) pointer address register value crc16 request eof - 8 bits ceh 02h 64 bits 8 bits 8 bits 16 bits - 1. gray color means that the field is optional. table 200. fast write dynamic configuration response format when error_flag is not set response sof response_flags crc16 response eof - 8 bits 16 bits - table 201. fast write dynamic configurati on response format when error_flag is set response sof response_flags error code crc16 response eof - 8 bits 8 bits 16 bits - figure 73. fast write dynamic configuration frame exchange between vcd and st25dvxxx vcd sof fast write dynamic configuration request eof st25dvxxx <-t 1 -> sof fast write dynamic configuration request eof docid027603 rev 4 169/220 ST25DV04K st25dv16k st25dv64k unique identifier (uid) 219 8 unique identifier (uid) the st25dvxxx is uniquely identified by a 64-bit unique identifier (uid). this uid complies with iso/iec 15963 and iso/iec 7816-6. the uid is a read-only code and comprises: ? eight msbs with a value of e0h, ? the ic manufacturer code ?st 02h? on 8 bits (iso/iec 7816-6/am1), ? a unique serial number on 48 bits. with the uid, each st25dvxxx can be addr essed uniquely and individually during the anticollision loop and for one-to-one exchanges betwee n a vcd and an st25dvxxx. table 202. uid format msb lsb 63 56 55 48 47 40 40 0 0xe0 0x02 st product code (1) unique serial number 1. see table 49: uid for st product code value definition. device parameters ST25DV04K st25dv16k st25dv64k 170/220 docid027603 rev 4 9 device parameters 9.1 maximum rating stressing the device ab ove the rating listed in table 203: absolute maximum ratings may cause permanent damage to the device. these are stress ratings only and operation of the device, at these or any other c onditions above those indicated in the operating sections of this specification, is not im plied. exposure to absolute maximum rating conditions for extended periods may affect the device reliability. device mission profile (application conditions) is compliant wit h jedec jesd47 qualification standard. extended mission profiles can be assessed on demand. refer also to the stmicroele ctronics sure program and other relevant quality documents. table 203. absolute maximum ratings symbol parameter min. ma x. unit t a ambient operating temperature range 6 all packages rf and i 2 c interfaces -40 85 c range 8 ufdfpn8, ufdfpn12 rf and i 2 c interfaces - 40 105 c so8n, tssop rf interface - 40 105 c i 2 c interface - 40 125 c t stg storage temperature sawn wafer on uv tape kept in its original packing form 15 25 c t stg retain - 9 (1) months t stg storage temperature ufdfpn8 (mlp8),so8n, tssop8, ufdfpn12, wlcsp10 - 65 150 c t lead lead temperature during soldering see note (2) c v io i 2 c input or output range - 0.50 6.5 v v dcg supply gpo cmos driver - 0.50 6.5 v v cc i 2 c supply voltage - 0.50 6.5 v i ol_max_sda dc output current on pin sda (when equal to 0) - 5 ma i ol_max_gpo_od dc output current on pin gpo open drain (when equal to 0) - 1.5 ma v max_1 (3) rf input voltage amplitude peak to peak between ac0 and ac1, v ss pin left floating v ac0 - v ac1 -11 v v max_2 (3) ac voltage between ac0 and v ss , or ac1 and v ss v ac0 - v ss , or v ac1 - v ss - 0.50 5.5 v v esd electrostatic discharge voltage (human body model) (4) all pins 2000 - v 1. counted from st production date. 2. compliant with jedec std j-std-020c (for small body, sn-pb or pb assembly), the st ecopack ? 7191395 specification, and the european directive on restrictions on hazardous substances (rohs) 2002/95/eu. 3. based on characterization, not tested in production. 4. aec-q100-002 (compliant with jedec st d jesd22-a114, c1 = 100 pf, r1 = 1500 , r2 = 500 ) docid027603 rev 4 171/220 ST25DV04K st25dv16k st25dv64k device parameters 219 9.2 i 2 c dc and ac parameters this section summarizes the operating and measurement conditions, and the dc and ac characteristics of the device in i 2 c mode. the parameters in the dc and ac characteristic tables that follow are derived from tests performed under the measurement conditions summarized in the relevant tables. designers should check that the op erating conditions in their circuit match the measurement conditions when relying on the quoted parameters. figure 74. ac test measurement i/o waveform table 204. i 2 c operating conditions sym bol parameter min. max. unit v cc supply voltage 1.8 5.5 v t a ambient operating temperature range 6 all packages -40 85 c range 8 ufdfpn8, ufdfpn12 -40 105 c so8n, tssop8 -40 125 c table 205. ac test measurement conditions symbol parameter min. max. unit c l load capacitance 100 pf t r, t f input rise and fall times - 50 ns v hi-lo input levels 0.2v cc to 0.8v cc v v ref(t) input and output timing reference levels 0.3v cc to 0.7v cc v table 206. input parameters symbol parameter min. max. unit c in input capacitance (sda) - 8 pf c in input capacitance (other pins) - 6 pf t ns (1) 1. characterized only. pulse width ignored (input filter on scl and sda) - 80 ns ! ) " 6 # # 6 # # 6 # # 6 # # ) n p u t a n d / u t p u t 4 i m i n g 2 e f e r e n c e , e v e l s ) n p u t , e v e l s device parameters ST25DV04K st25dv16k st25dv64k 172/220 docid027603 rev 4 table 207. i 2 c dc characteristics up to 85c symbol parameter test condition min. typ. max. unit i li input leakage current (scl, sda) v in = v ss or v cc device in standby mode -0.03 0.1a i li input leakage current (lpd) v in = v ss device in standby mode -0.1 0.5a i lo output leakage current (sda) sda in hi-z, external voltage applied on sda: v ss or v cc -0.03 0.1a i cc _e 2 operating supply current (device select e 2 address) read (1) v cc = 1.8 v, f c = 1mhz (rise/fall time < 50 ns) -116 160 a v cc = 3.3 v, f c = 1mhz (rise/fall time < 50 ns) - 220 240 v cc = 5.5 v, f c = 1mhz (rise/fall time < 50 ns) - 510 550 i cc _mb operating supply current (device select mb address) read (1) v cc = 1.8 v, f c = 1mhz (rise/fall time < 50 ns) -116 160 a v cc = 3.3 v, f c = 1mhz (rise/fall time < 50 ns) - 220 240 v cc = 5.5 v, f c = 1mhz (rise/fall time < 50 ns) - 510 550 i cc0 operating supply current (device select e 2 address) write (1) v cc = 1.8 v, f c = 1mhz (rise/fall time < 50 ns) -110 300 a v cc = 3.3 v, f c = 1mhz (rise/fall time < 50 ns) -110 330 v cc = 5.5 v, f c = 1mhz (rise/fall time < 50 ns) - 130 430 i cc0 _mb operating supply current (device select mb address) write (1) v cc = 1.8 v, f c = 1mhz (rise/fall time < 50 ns) - 170 200 a v cc = 3.3 v, f c = 1mhz (rise/fall time < 50 ns) - 280 300 v cc = 5.5 v, f c = 1mhz (rise/fall time < 50 ns) - 520 600 i cc1 (lpd = 1) low power down supply current v cc = 1.8 v - 0.84 1.5 a v cc = 3.3 v - 1.3 2 v cc = 5.5 v - 1.7 3 i cc1 _pon (lpd = 0) static standby supply current after power on or device select stop or time out v cc = 1.8 v - 72 100 a v cc = 3.3 v - 76 100 v cc = 5.5 v - 87 120 docid027603 rev 4 173/220 ST25DV04K st25dv16k st25dv64k device parameters 219 v il input low voltage (sda, scl) v cc = 1.8 v - 0.45 - 0.25 v cc v v cc = 3.3 v - 0.45 - 0.3 v cc v cc = 5.5 v - 0.45 - 0.3 v cc v il_lpd input low voltage (lpd) v cc = 3.3 v - 0.45 - 0.2 v cc v v ih input high voltage (sda, scl) v cc = 1.8 v 0.75 v cc -v cc + 1 v v cc = 3.3 v 0.75 v cc -v cc + 1 v cc = 5.5 v 0.75 v cc -v cc + 1 v ih _lpd input high voltage (lpd) v cc = 1.8 v 0.85 v cc -v cc + 1 v v cc = 3.3 v 0.85 v cc -v cc + 1 v cc = 5.5 v 0.85 v cc -v cc + 1 v ol _sda output low voltage sda (1 mhz) i ol = 1 ma, v cc = 1.8 v - 0.05 0.4 v i ol = 2.1 ma, v cc = 3.3 v - 0.075 0.4 i ol = 3 ma, v cc = 5.5 v - 0.09 0.4 v cc _power_up device select acknowledge f c = 100 khz - 1.48 1.7 v 1. scl, sda connected to ground or v cc. sda connected to v cc through a pull-up resistor. table 207. i 2 c dc characteristics up to 85c (continued) symbol parameter test condition min. typ. max. unit device parameters ST25DV04K st25dv16k st25dv64k 174/220 docid027603 rev 4 table 208. i 2 c dc characteristics up to 125c symbol parameter test condition min. typ. max. unit i li input leakage current (scl, sda) v in = v ss or v cc device in standby mode -0.03 0.1a i li input leakage current (lpd) v in = v ss device in standby mode -0.1 0.5a i lo output leakage current (sda) sda in hi-z, external voltage applied on sda: v ss or v cc -0.03 0.1a i cc _e 2 operating supply current (device select e 2 address) read (1) v cc = 1.8 v, f c = 1mhz (rise/fall time < 50 ns) - 126 180 a v cc = 3.3 v, f c = 1mhz (rise/fall time < 50 ns) - 230 260 v cc = 5.5 v, f c = 1mhz (rise/fall time < 50 ns) - 510 550 i cc _mb operating supply current (device select mb address) read (1) v cc = 1.8 v, f c = 1mhz (rise/fall time < 50 ns) - 126 180 a v cc = 3.3 v, f c = 1mhz (rise/fall time < 50 ns) - 230 260 v cc = 5.5 v, f c = 1mhz (rise/fall time < 50 ns) - 510 550 i cc0 operating supply current (device select e 2 address) write (1) v cc = 1.8 v, f c = 1mhz (rise/fall time < 50 ns) - 120 310 a v cc = 3.3 v, f c = 1mhz (rise/fall time < 50 ns) - 120 350 v cc = 5.5 v, f c = 1mhz (rise/fall time < 50 ns) - 140 450 i cc0 _mb operating supply current (device select mb address) write (1) v cc = 1.8 v, f c = 1mhz (rise/fall time < 50 ns) - 180 220 a v cc = 3.3 v, f c = 1mhz (rise/fall time < 50 ns) - 290 320 v cc = 5.5 v, f c = 1mhz (rise/fall time < 50 ns) - 520 600 i cc1 (lpd = 1) low power down supply current v cc = 1.8 v - 2.5 5 a v cc = 3.3 v - 3 6 v cc = 5.5 v - 4 7 i cc1 _pon (lpd = 0) static standby supply current after power on or device select stop or time out v cc = 1.8 v - 78 110 a v cc = 3.3 v - 82 110 v cc = 5.5 v - 95 130 v il input low voltage (sda, scl) v cc = 1.8 v - 0.45 - 0.25 v cc v v cc = 3.3 v - 0.45 - 0.3 v cc v cc = 5.5 v - 0.45 - 0.3 v cc docid027603 rev 4 175/220 ST25DV04K st25dv16k st25dv64k device parameters 219 v il_lpd input low voltage (lpd) v cc = 3.3 v - 0.45 - 0.2 v cc v v ih input high voltage (sda, scl) v cc = 1.8 v 0.75 v cc -v cc + 1 v v cc = 3.3 v 0.75 v cc -v cc + 1 v cc = 5.5 v 0.75 v cc -v cc + 1 v ih _lpd input high voltage (lpd) v cc = 1.8 v 0.85 v cc -v cc + 1 v v cc = 3.3 v 0.85 v cc -v cc + 1 v cc = 5.5 v 0.85 v cc -v cc + 1 v ol _sda output low voltage sda (1 mhz) i ol = 1 ma, v cc = 1.8 v - 0.05 0.4 v i ol = 2.1 ma, v cc = 3.3 v - 0.08 0.4 i ol = 3 ma, v cc = 5.5 v - 0.1 0.4 v cc _power_up device select acknowledge f c = 100 khz - 1.48 1.7 v 1. scl, sda connected to ground or v cc. sda connected to v cc through a pull-up resistor. table 208. i 2 c dc characteristics up to 125c (continued) symbol parameter test condition min. typ. max. unit device parameters ST25DV04K st25dv16k st25dv64k 176/220 docid027603 rev 4 table 209. i 2 c ac characteristics up to 85c test conditions specified in table 204 symbol alt. parameter min. max. unit f c f scl clock frequency 0.05 1000 khz t chcl t high clock pulse width high 0.26 25000 (1) s t clch t low clock pulse width low 0.5 25000 (2) s t start_out - i2c timeout on start condition 35 - ms t xh1xh2 t r input signal rise time (3) (3) ns t xl1xl2 t f input signal fall time (3) (3) ns t dl1dl2 (4) t f sda (out) fall time 20 120 ns t dxcx t su:dat data in set up time 0 - ns t cldx t hd:dat data in hold time 0 - ns t clqx (5) t dh data out hold time 100 - ns t clqv (6) t aa clock low to next data valid (access time) - 450 ns t chdx (7) t su:sta start condition set up time 250 - ns t dlcl t hd:sta start condition hold time 0.25 35000 (8) s t chdh t su:sto stop condition set up time 250 - ns t dhdl t buf time between stop condition and next start condition 500 - ns t w - i2c write time (9) -5ms t bootdc - rf off and lpd = 0 - 0.6 ms t bootlpd -rf off - 0.6 ms 1. t chcl timeout. 2. t clch timeout. 3. there is no min. or max. values for the input signal rise and fall times. it is however recommended by the i 2 c specification that the input signal rise and fall times be less than 120 ns when f c < 1 mhz. 4. characterized on bench. 5. to avoid spurious start and stop conditions, a mini mum delay is placed between scl=1 and the falling or rising edge of sda. 6. t clqv is the time (from the falling edge of scl) required by the sda bus line to reach 0.8v cc in a compatible way with the i 2 c specification (which specifies t su:dat (min) = 100 ns), assuming that the r bus c bus time constant is less than 150 ns (as specified in the figure 76: i 2 c fast mode (f c = 1 mhz): maximum r bus value versus bus parasitic capacitance (c bus ) ). 7. for a restart condition, or following a write cycle. 8. t dlcl timeout. 9. i 2 c write time for 1 byte, 2 bytes, 3 bytes or 4 by tes in eeprom (user memory and system configuration), provided they are all located in the same memory page , that is the most significant memory address bits (b16- b2) are the same. docid027603 rev 4 177/220 ST25DV04K st25dv16k st25dv64k device parameters 219 table 210. i 2 c ac characteristics up to 125c test conditions specified in table 204 symbol alt. parameter min. max. unit f c f scl clock frequency 0.05 1000 khz t chcl t high clock pulse width high 0.26 25000 (1) s t clch t low clock pulse width low 0.5 25000 (2) s t start_out - i2c timeout on start condition 35 - ms t xh1xh2 t r input signal rise time (3) (3) ns t xl1xl2 t f input signal fall time (3) (3) ns t dl1dl2 (4) t f sda (out) fall time 20 120 ns t dxcx t su:dat data in set up time 0 - ns t cldx t hd:dat data in hold time 0 - ns t clqx (5) t dh data out hold time 100 - ns t clqv (6) t aa clock low to next data valid (access time) - 450 ns t chdx (7) t su:sta start condition set up time 250 - ns t dlcl t hd:sta start condition hold time 0.25 35000 (8) s t chdh t su:sto stop condition set up time 250 - ns t dhdl t buf time between stop condition and next start condition 500 - ns t w - i2c write time (9) -5.5ms t bootdc - rf off and lpd = 0 - 0.6 ms t bootlpd -rf off - 0.6 ms 1. t chcl timeout. 2. t clch timeout. 3. there is no min. or max. values for the input signal rise and fall times. it is however recommended by the i 2 c specification that the input signal rise and fall times be less than 120 ns when f c < 1 mhz. 4. characterized on bench. 5. to avoid spurious start and stop conditions, a mini mum delay is placed between scl=1 and the falling or rising edge of sda. 6. t clqv is the time (from the falling edge of scl) required by the sda bus line to reach 0.8v cc in a compatible way with the i 2 c specification (which specifies t su:dat (min) = 100 ns), assuming that the r bus c bus time constant is less than 150 ns (as specified in the figure 76: i 2 c fast mode (f c = 1 mhz): maximum r bus value versus bus parasitic capacitance (c bus ) ). 7. for a restart condition, or following a write cycle. 8. t dlcl timeout. 9. i 2 c write time for 1 byte, 2 bytes, 3 bytes or 4 by tes in eeprom (user memory and system configuration), provided they are all located in the same memory page , that is the most significant memory address bits (b16- b2) are the same. device parameters ST25DV04K st25dv16k st25dv64k 178/220 docid027603 rev 4 figure 75. i 2 c ac waveforms 3 # , 3 $ ! ) n 3 # , 3 $ ! / u t 3 # , 3 $ ! ) n t # ( # , t $ , # , t # ( $ 8 3 t a r t c o n d i t i o n t # , # ( t $ 8 # 8 t # , $ 8 3 $ ! ) n p u t 3 $ ! # h a n g e t # ( $ ( t $ ( $ , 3 t o p c o n d i t i o n $ a t a v a l i d t # , 1 6 t # , 1 8 t # ( $ ( 3 t o p c o n d i t i o n t # ( $ 8 3 t a r t c o n d i t i o n 7 r i t e c y c l e t 7 ! ) e 3 t a r t c o n d i t i o n t # ( # , t 8 ( 8 ( t 8 ( 8 ( t 8 , 8 , t 8 , 8 , $ a t a v a l i d t $ , $ , docid027603 rev 4 179/220 ST25DV04K st25dv16k st25dv64k device parameters 219 figure 76 indicates how the value of the pull-up resistor can be calculated. in most applications, though, this method of synchronization is not employed, and so the pull-up resistor is not necessary, prov ided that the bus master has a push-pull (rather than open drain) output. figure 76. i 2 c fast mode (f c = 1 mhz): maximum r bus value versus bus parasitic capacitance (c bus ) 9.3 gpo characteristics this section summarizes the operating and m easurement conditions of the gpo feature. the parameters in the dc and ac characteristic tables that follow are derived from tests performed under the measurement conditi ons summarized in the relevant tables. % x v o l q h f d s d f l w r u s ) % x v o l q h s x o o x s u h v l v w r u . ? 0 6 y 9 , e & e x v p d v w h u 6 7 ' 9 5 e x v 9 & & & e x v 6 & / 6 ' $ + h u h 5 e x v ? & e x v q v 5 e x v ? & e x v q v 7 k h 5 e x v [ & e x v w l p h f r q v w d q w p x v w e h e h o r z q v 7 k h w l p h f r q v w d q w o l q h l v u h s u h v h q w h g r q w k h o h i w table 211. gpo dc characteristics up to 85c symbol parameter condition min typ max unit v ol _gpo_cmos output low voltage (gpo cmos) v dcg = 1.8 v, i ol = 0.5 ma - - 0.4 v v dcg = 3.3 v, i ol = 0.5 ma - - 0.4 v dcg = 5.5 v, i ol = 0.5 ma - - 0.4 v oh _gpo_cmos output high voltage (gpo cmos) v dcg = 1.8 v, i oh = - 0.5 ma v dcg - 0.4 - - v v dcg = 3.3 v, i oh = - 0.5 ma v dcg - 0.4 - - v dcg = 5.5 v, i oh = - 0.5 ma v dcg - 0.4 - - v ol _gpo_od output low voltage (gpo open drain) iol = 1 ma, vcc = 1.8 v - 0.28 0.4 v iol = 1 ma, vcc = 3.3 v - 0.20 0.4 iol = 1 ma, vcc = 5.5 v - 0.20 0.4 i l _gpo_od output leakage (gpo open drain) gpo in hi-z, external voltage applied on: gpo, v ss or v cc - 0.15 0.06 0.15 a i li _v dgc input leakage (v dgc )v dgc = 5.5 v - - 0.1 a device parameters ST25DV04K st25dv16k st25dv64k 180/220 docid027603 rev 4 9.4 rf electrical parameters this section summarizes the operating and measurement conditions, and the dc and ac characteristics of the device in rf mode. the parameters in the dc and ac characterist ics tables that follow are derived from tests performed under the measurement conditi ons summarized in the relevant tables. designers should check that the operating cond itions in their circuit match the measurement conditions when relying on the quoted parameters. table 212. gpo dc characteristics up to 125c symbol parameter condition min typ max unit v ol _gpo_cmos output low voltage (gpo cmos) v dcg = 1.8 v, i ol = 0.5 ma - - 0.4 v v dcg = 3.3 v, i ol = 0.5 ma - - 0.4 v dcg = 5.5 v, i ol = 0.5 ma - - 0.4 v oh _gpo_cmos output high voltage (gpo cmos) v dcg = 1.8 v, i oh = - 0.5 ma v dcg - 0.4 - - v v dcg = 3.3 v, i oh = - 0.5 ma v dcg - 0.4 - - v dcg = 5.5 v, i oh = - 0.5 ma v dcg - 0.4 - - v ol _gpo_od output low voltage (gpo open drain) iol = 1 ma, vcc = 1.8 v - 0.28 0.4 v iol = 1 ma, vcc = 3.3 v - 0.22 0.4 iol = 1 ma, vcc = 5.5 v - 0.21 0.4 i l _gpo_od output leakage (gpo open drain) gpo in hi-z, external voltage applied on gpo: v ss or v cc - 0.15 0.06 0.15 a i li _v dgc input leakage (v dgc )v dgc = 5.5 v - - 0.1 a table 213. gpo ac characteristics symbol parameter condition min max unit t r _gpo_cmos output rise time c l = 30 pf, v dcg = 1.8 v to 5.5 v - 50 ns t f _gpo_cmos output fall time c l = 30 pf, v dcg = 1.8 v to 5.5 v - 50 table 214. rf characteristics (1)(2) symbol parameter condition min typ max unit f cc external rf signal frequency - 13.553 13.56 13.5 67 mhz h_iso operating field according to iso range 6 t a = -40 c to 85 c 150 - 5000 ma/m range 8 t a = -40 c to 105 c mi carrie r 10% carrier modulation index (3) mi=(a-b)/(a+b) 150 ma/m > h_iso > 1000 ma/m 10 - 30 % 100% carrier modulation index mi=(a-b)/(a+b) (4) 95 - 100 t min cd minimum time from carrier generation to first data from h-field min - - 1 ms docid027603 rev 4 181/220 ST25DV04K st25dv16k st25dv64k device parameters 219 f sh subcarrier frequency high f cc /32 - 423.7 5 -khz f sl subcarrier frequency low f cc /28 - 484.2 8 -khz t 1 time for st25dvxxx response 4352/f c 318.6 320.9 323. 3 s t 2 time between commands 4192/f c 309 311.5 314 s t 3 time between commands 4384/f c 323.3 - - s w t _block rf user memory write time (including internal verify) (5) 1 block - 5.2 - ms 4 blocks - 19.7 - ms w t _byte rf system memory write time including internal verify) (5) 1 byte - 4.9 - ms w t _mb rf mailbox write time (from vcd request sof to st25dvxxx response eof) (5)(6) 256 byte - 80.7 - ms read_mb rf mailbox read time (from vcd request sof to st25dvxxx response eof) (5)(6) 256 byte - 81 - ms c tun internal tuning capacitor in so8n (6) f = 13.56 mhz 26.5 28.5 30.5 pf v back backscattered level as defined by iso test -10--mv v min_1 (3) rf input voltage amplitude between ac0 and ac1, v ss pin left floating, vac0-vac1 peak to peak (3) inventory and read operations - 4.8 - v write operations - 5.25 - v v min_2 (3) ac voltage between ac0 and v ss or between ac1 and v ss (3) inventory and read operations - 2.25 - v write operations - 2.7 - v t bootrf without dc supply (no v cc ) set up time - 0.6 - ms t rf_off rf off time chip reset 2 - - ms 1. t a = -40 to 105 c. characterized only. 2. all timing characterizations were performed on a reference antenna with the following characteristics: iso antenna class1 tuning frequency = 13.7 mhz 3. characterized on bench. 4. characterized at room temperature only, on wafer at por level. 5. for vcd request coded in 1 out of 4 and st25dvxxx response in hi gh data rate, single sub carrier. 6. the tuning capacitance value is measured with st characterization equipment at chip power on reset. this value is used as reference for antenna design. minimum and maximum values come from correlation with industrial tester limits. table 214. rf characteristics (1)(2) (continued) symbol parameter condition min typ max unit device parameters ST25DV04K st25dv16k st25dv64k 182/220 docid027603 rev 4 figure 77: ask modulated signal shows an ask modulated sign al from the vcd to the st25dvxxx. the test conditions for the ac/dc parameters are: ? close coupling condition with tester antenna (1 mm) ? st25dvxxx performance measur ed at the tag antenna ? st25dvxxx synchronous timing , transmit and receive figure 77. ask modulated signal table 215. operating conditions symbol parameter min. max. unit t a ambient operating temperature range 6 -40 85 c range 8 -40 105 - 3 6 $ % w 5 ) ) w 5 ) 5 w 5 ) 6 % / w 0 , 1 & ' i & & docid027603 rev 4 183/220 ST25DV04K st25dv16k st25d v64k package information 219 10 package information in order to meet environmental requirements, st offers these devices in different grades of ecopack ? packages, depending on their level of environmental compliance. ecopack ? specifications, grade definitions a nd product status are available at: www.st.com . ecopack ? is an st trademark. 10.1 so8n package information figure 78. so8n ? 8-lead, 4.9 x 6 mm, plas tic small outline, 150 mils body width, package outline 1. drawing is not to scale. table 216. so8n ? 8-lead 4.9 x 6 mm, pl astic small outline, 150 mils body width, package mechanical data symbol millimeters inches (1) min. typ. max. min. typ. max. a - - 1.750 - - 0.0689 a1 0.100 - 0.250 0.0039 - 0.0098 a2 1.250 - - 0.0492 - - b 0.280 - 0.480 0.0110 - 0.0189 c 0.170 - 0.230 0.0067 - 0.0091 d 4.800 4.900 5.000 0.1890 0.1929 0.1969 e 5.800 6.000 6.200 0.2283 0.2362 0.2441 e1 3.800 3.900 4.000 0.1496 0.1535 0.1575 e - 1.270 - - 0.0500 - 6 2 $ b 9 % c c c b $ c % h x ? ! k p p , ! * $ 8 * ( 3 / $ 1 ( e ! , package information ST25DV04K st25dv16k st25dv64k 184/220 docid027603 rev 4 10.2 tssop8 package information figure 79.tssop8 ? 8-lead thin shrink small outline, 3 x 6.4 mm, 0.65 mm pitch, package outline 1. drawing is not to scale. h 0.250 - 0.500 0.0098 - 0.0197 k 0 - 8 0 - 8 l 0.400 - 1.270 0.0157 - 0.0500 l1 - 1.040 - - 0.0409 - ccc - - 0.100 - - 0.0039 1. values in inches are converted fr om mm and rounded to four decimal digits. table 216. so8n ? 8-lead 4.9 x 6 mm, pl astic small outline, 150 mils body width, package mechanical data (continued) (continued) symbol millimeters inches (1) min. typ. max. min. typ. max. table 217. tssop8 ? 8-lead thin shrink small outline, 3 x 6.4 mm, 0.65 mm pitch, package mechanical data symbol millimeters inches (1) min. typ. max. min. typ. max. a - - 1.200 - - 0.0472 a1 0.050 - 0.150 0.0020 - 0.0059 a2 0.800 1.000 1.050 0.0315 0.0394 0.0413 b 0.190 - 0.300 0.0075 - 0.0118 c 0.090 - 0.200 0.0035 - 0.0079 7 6 6 2 3 $ 0 b 9 w > r e > ? ?? docid027603 rev 4 185/220 ST25DV04K st25dv16k st25d v64k package information 219 cp - - 0.100 - - 0.0039 d 2.900 3.000 3.100 0.1142 0.1181 0.1220 e - 0.650 - - 0.0256 - e 6.200 6.400 6.600 0.2441 0.2520 0.2598 e1 4.300 4.400 4.500 0.1693 0.1732 0.1772 l 0.450 0.600 0.750 0.0177 0.0236 0.0295 l1 - 1.000 - - 0.0394 - 0 - 8 0 - 8 1. values in inches are converted fr om mm and rounded to four decimal digits. table 217. tssop8 ? 8-lead thin shrink small outline, 3 x 6.4 mm, 0.65 mm pitch, package mechanical data (continued) symbol millimeters inches (1) min. typ. max. min. typ. max. package information ST25DV04K st25dv16k st25dv64k 186/220 docid027603 rev 4 10.3 ufdfn8 package information figure 80. ufdfn8 - 8-lead, 2 3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat package outline 1. max. package warpage is 0.05 mm. 2. exposed copper is not systematic and can appear parti ally or totally according to the cross section. 3. drawing is not to scale. table 218. ufdfn8 - 8-lead, 2 3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat package mechanical data symbol millimeters inches (1) min typ max min typ max a 0.450 0.550 0.600 0.0177 0.0217 0.0236 a1 0.000 0.020 0.050 0.0000 0.0008 0.0020 b (2) 0.200 0.250 0.300 0.0079 0.0098 0.0118 d 1.900 2.000 2.100 0.0748 0.0787 0.0827 d2 1.200 - 1.600 0.0472 - 0.0630 e 2.900 3.000 3.100 0.1142 0.1181 0.1220 e2 1.200 - 1.600 0.0472 - 0.0630 = : e b 0 ( b 9 7 r s y l h z 3 l q , ' p d u n l q j 6 l g h y l h z 6 h d w l q j s o d q h h h h f f f & & & & % $ 1 ' ( d d d d d d $ $ $ [ [ ' d w x p $ 7 h u p l q d o w l s ' h w d l o 3 $ ( y h q w h u p l q d o / / / h h 3 l q , ' p d u n l q j % r w w r p y l h z 6 h h ' h w d l o 3 $ h h 1 ' [ ' / / ( . / e docid027603 rev 4 187/220 ST25DV04K st25dv16k st25d v64k package information 219 e - 0.500 - 0.0197 k 0.300 - - 0.0118 - - l 0.300 - 0.500 0.0118 - 0.0197 l1 - - 0.150 - - 0.0059 l3 0.300 - - 0.0118 - - aaa - - 0.150 - - 0.0059 bbb - - 0.100 - - 0.0039 ccc - - 0.100 - - 0.0039 ddd - - 0.050 - - 0.0020 eee (3) - - 0.080 - - 0.0031 1. values in inches are converted from mm and rounded to 4 decimal digits. 2. dimension b applies to plated terminal and is meas ured between 0.15 and 0.30 mm from the terminal tip. 3. applied for exposed die paddle and terminals. ex clude embedding part of exposed die paddle from measuring. table 218. ufdfn8 - 8-lead, 2 3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat package mechanical data (continued) symbol millimeters inches (1) min typ max min typ max package information ST25DV04K st25dv16k st25dv64k 188/220 docid027603 rev 4 10.4 ufdfpn12 package information figure 81. ufdfpn12 - 12-lead, 3x3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat package outline 1. drawing is not to scale. 2. preliminary drawing. table 219. ufdfpn12 - 12-lead, 3x3 mm, 0.5 mm pitch ultra thin profile fine pitch dual flat package mechanical data (1) 1. preliminary data. symbol millimeters inches (2) 2. values in inches are converted from mm and rounded to 4 decimal digits. min typ max min typ max a (3) 3. package total thickness. 0.45 0.55 0.60 0.0177 0.0217 0.0236 b 0.20 0.25 0.30 0.0079 0.0098 0.0118 d 2.95 3.00 3.10 0.1161 0.1181 0.1220 d2 1.35 1.40 1.45 0.0531 0.0551 0.0571 e 0.50 0.0197 e 2.95 3.00 3.10 0.1161 0.1181 0.1220 e2 2.50 2.55 2.60 0.0984 0.1004 0.1024 l 0.25 0.30 0.35 0.0098 0.0118 0.0138 k 0.40 0.0157 8 ) ' ) 3 1 b & b 0 ( b 9 h e % 2 7 7 2 0 9 , ( : ' ( 7 2 3 9 , ( : 6 , ' ( 9 , ( : ' / ( n 3 l q , ' p d u n l q j $ docid027603 rev 4 189/220 ST25DV04K st25dv16k st25d v64k package information 219 10.5 wlcsp10 package information figure 82. wlcsp - 10 balls, 1.649x1.483 mm, 0.4 mm pitch, wafer level chip scale package outline 1. drawing is not to scale. 2. dimension is measured at the maximum bum p diameter parallel to primary datum z. 3. primary datum z and seating plane are defined by the spherical crowns of the bump. 4. bump position designation per jesd 95-1, spp-010. table 220. wlcsp - 10 balls, 1.649x1.483 mm, 0.4 mm pitch, wafer level chip scale mechanical data symbol millimeters inches (1) min typ max min typ max a 0.265 0.295 0.325 0.0104 0.0116 0.0128 a1 - 0.095 - - 0.0037 - a2 - 0.175 - - 0.0069 - a3 - 0.025 - - 0.0010 - b - 0.185 - - 0.0073 - d - 1.649 1.669 - 0.0649 0.0657 e - 1.483 1.503 - 0.0584 0.0592 e - 0.400 - - 0.0157 - e1 - 0.800 - - 0.0315 - % 9 b : / & 6 3 b 0 ( b 9 ; $ $ $ e e e $ h , + h ' * ' ( 7 $ , / $ 2 u l h q w d w l r q u h i h u h q f h < ( d d d ; 6 , ' ( 9 , ( : % 2 7 7 2 0 9 , ( : 7 2 3 9 , ( : ' ( 7 $ , / $ 5 2 7 $ 7 ( ' f f f 0 = ; < g g g 0 = = $ e [ h h h = 6 ( $ 7 , 1 * 3 / $ 1 ( % 8 0 3 - ) package information ST25DV04K st25dv16k st25dv64k 190/220 docid027603 rev 4 figure 83. wlcsp - 10 balls, 1.649x1.483 mm, 0.4 mm pitch, wafer level chip scale recommended footprint 1. dimensions are expr essed in millimeters. h - 0.346 - - 0.0136 - i - 1.039 - - 0.0409 - j - 0.200 - - 0.0079 - f - 0.314 - - 0.0124 - g - 0.342 - - 0.0135 - aaa - 0.110 - - 0.0043 - bbb - 0.110 - - 0.0043 - ccc - 0.110 - - 0.0043 - ddd - 0.060 - - 0.0024 - eee - 0.060 - - 0.0024 - 1. values in inches are converted from mm and rounded to 4 decimal digits. table 220. wlcsp - 10 balls, 1.649x1.483 mm, 0.4 mm pitch, wafer level chip scale mechanical data (continued) symbol millimeters inches (1) min typ max min typ max % 9 b : / & 6 3 b ) 3 b 9 docid027603 rev 4 191/220 ST25DV04K st25dv16k st25dv64k ordering information 219 11 ordering information table 221. ordering information scheme example: st25dv 64k -jf r 6 d 3 device type st25dv = dynamic nfc/rfid tag based on iso 15693 and nfc t5t memory size 04k = 4 kbits 16k = 16 kbits 64k = 64 kbits device features ie = i 2 c & gpo open drain, fast transfer mode & energy harvesting jf = i 2 c & gpo cmos, fast transfer mode, energy harvesting & low power mode operating voltage r = v cc = 1.8 to 5.5 v device grade 6 = industrial: device tested with standard test flow over - 40 to 85 c 8 = industrial device tested with standard test flow over -40 to 105 c (ufdfpn8 and ufdfpn12 only) or over -40 to 125 c (so8n and tssop8 only, 105 c only for rf interface) package d = ufdfpn12 s = so8n t = tssop8 c = ufdfpn8 (only for 04k version) u = 725 m +/- 20 m unsawn wafer (only for 04k version) l = wlcsp (thin 10 balls) (only for 04k version) capacitance 3 = 28.5 pf ordering information ST25DV04K st25dv16k st25dv64k 192/220 docid027603 rev 4 note: parts marked as ?es? or ?e? are not yet qualified and therefore not approved for use in production. st is not responsi ble for any consequences resulti ng from such use. in no event will st be liable for the customer using any of these engineering samp les in production. st?s quality department must be contacted pr ior to any decision to use these engineering samples to run a qua lification activity. docid027603 rev 4 193/220 ST25DV04K st25dv16k st25dv64k bit representation and coding for fast commands 219 appendix a bit representation and coding for fast commands data bits are encoded using manchester codi ng, according to the following schemes. for the low data rate, same subcarri er frequency or frequencies is/are used. in this case, the number of pulses is multiplied by 4 and all times increase by this factor. for the fast commands using one subcarrier, all pulse numbers and times are divided by 2. a.1 bit coding using one subcarrier a.1.1 high data rate for the fast commands, a logic 0 starts with four pulses at 423.75 khz (f c /32) followed by an unmodulated time of 9.44 s, as shown in figure 84 . figure 84. logic 0, high data rate, fast commands for the fast commands, a logic 1 starts with an unmodulated time of 9.44 s followed by four pulses of 423.75 khz (f c /32), as shown in figure 85 . figure 85. logic 1, high data rate, fast commands a.1.2 low data rate for the fast commands, a logic 0 starts with 16 pulses at 423.75 khz (f c /32) followed by an unmodulated time of 37.76 s, as shown in figure 86 . figure 86. logic 0, low data rate, fast commands for the fast commands, a logic 1 starts with an unmodulated time of 37.76 s followed by 16 pulses at 423.75 khz (f c /32), as shown in figure 87 . ? v d l e ? v d l e ? v d l e bit representation and coding for fast commands ST25DV04K st25dv16k st25dv64k 194/220 docid027603 rev 4 figure 87. logic 1, low data rate, fast commands note: for fast commands, bit coding using two subcarriers is not supported. a.2 st25dvxxx to vcd frames frames are delimited by an sof and an eof. they are implemented using code violation. unused options are reserved for future use. for the low data rate, the same subcarrier frequency or frequencies is/are used. in this ca se, the number of pulses is multiplied by 4. for the fast commands using one subcarrier, all pulse numbers and times are divided by 2. a.3 sof when using one subcarrier a.3.1 high data rate for the fast commands, the sof comprises an unmodulated time of 28.32 s, followed by 12 pulses at 423.75 khz (f c /32), and a logic 1 that consists of an unmodulated time of 9.44 s followed by four pulses at 423.75 khz, as shown in figure 88 . figure 88. start of frame, high data rate, one subcarrier, fast commands a.3.2 low data rate for the fast commands, the sof comprises an unmodulated time of 113.28 s, followed by 48 pulses at 423.75 khz ( f c /32), and a logic 1 that includes an unmodulated time of 37.76 s followed by 16 pulses at 423.75 khz, as shown in figure 89 . figure 89. start of frame, low data rate, one subcarrier, fast commands ? v $ l e ?xe r? ]?? ?x?? r? ? v d l e ? v docid027603 rev 4 195/220 ST25DV04K st25dv16k st25dv64k bit representation and coding for fast commands 219 a.4 eof when using one subcarrier a.4.1 high data rate for the fast commands, the eof comprises a logic 0 that includes four pulses at 423.75 khz and an unmodulated time of 9.44 s, followed by 12 pulses at 423.75 khz ( f c /32) and an unmodulated time of 37.76 s, as shown in figure 90 . figure 90. end of frame, high data rate, one subcarrier, fast commands a.4.2 low data rate for the fast commands, the eof comprises a lo gic 0 that includes 16 pulses at 423.75 khz and an unmodulated time of 37.76 s, followed by 48 pulses at 423.75 khz ( f c /32) and an unmodulated time of 113.28 s, as shown in figure 91 . figure 91. end of frame, low data rate, one subcarrier, fast commands note: for sof and eof in fast commands, bit coding using two subcarriers is not supported. ?xe r? d l e ?x?? r? ??x? r? ]?? ?x?? r? i2c sequences ST25DV04K st25dv16k st25dv64k 196/220 docid027603 rev 4 appendix b i 2 c sequences b.1 device select codes b.2 i 2 c byte writing and polling b.2.1 i 2 c byte write in user memory table 222. st25dvxxx device select usage millimeters comment hexadecimal binary - 1010 e2 11 r/w dev select generic e2 = 0b user memory, dynamic registers, ftm mailbox e2 = 1b system memory a6h 1010 0110b user memory, dynamic registers, ftm mailbox writing a7h 1010 0111b user memory, dynamic registers, ftm mailbox reading aeh 1010 1110b system memory writing afh 1010 1111b system memory reading table 223. byte write in user me mory when write operation allowed request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit data - send data (1 byte) - ack 9th bit stop - start of programming docid027603 rev 4 197/220 ST25DV04K st25dv16k st25dv64k i2c sequences 219 table 224. polling during programming after byte writing in user memory request/response frame comment master drives sda slave drives sda start a6h - device select for writing - noack 9th bit device busy start a6h - device select for writing - noack 9th bit device busy ... ... device select for writing ... ... ... 9th bit device busy start a6h - device select for writing -ack 9th bit device ready programing completed stop - end of polling table 225. byte write in user memory when write operation is not allowed request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit data - send data - noack 9th bit: write access not granted or ftm activated. stop - no programming device return in standby i2c sequences ST25DV04K st25dv16k st25dv64k 198/220 docid027603 rev 4 b.2.2 i 2 c byte writing in dynami c registers and polling table 226. byte write in dynamic register (if not read only) request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit dynamic register address_lsb - send address lsb (1 byte) dynamic register are located from address 2000h to 2007h , some are only readable - ack 9th bit data - send data - ack 9th bit stop - immediate update of dynamic register table 227. polling during programming after byte write in dynamic register request/response frame comment master drives sda slave drives sda start a6h - device select for writing -ack 9th bit device busy dynamic register updates is immediate stop - end of polling table 228. byte write in dynamic register if read only request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit 20h - send address msb (1 byte) - noack 9th bit docid027603 rev 4 199/220 ST25DV04K st25dv16k st25dv64k i2c sequences 219 b.2.3 i 2 c byte write in mailbox and polling ro dynamic register address_lsb - send address lsb (1 byte) addresses 2001h, 2004h, 2005h and 2007h are read only registers. - ack 9th bit data - send data - noack 9th bit stop - no programming device return in standby table 228. byte write in dynamic register if read only (continued) request/response frame comment master drives sda slave drives sda table 229. byte write in mailbox when mailbox is free from rf message and fast transfer mode is activated request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit 20h - send mailbox address msb (1 byte) - ack 9th bit 08h - send address lsb (1 byte) write must be done at first address of mailbox - ack 9th bit data - send data - ack 9th bit stop - immediate update of mailbox i2c sequences ST25DV04K st25dv16k st25dv64k 200/220 docid027603 rev 4 b.2.4 i 2 c byte write and polling in system memory table 230. byte write in mailbox when mailbox is not free from rf message fast transfer mode is not activated request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit 20h - send mailbox address msb (1 byte) - ack 9th bit 08h - send address lsb (1 byte) write must be done at first address of mailbox - ack 9th bit data - send data -noack 9th bit access mailbox busy or ftm not activated stop - no programming device return in standby table 231. byte write in system memory if i 2 c security session is open and register is not ro request/response frame comment master drives sda slave drives sda start aeh - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit data - send data - ack 9th bit stop - start of programming docid027603 rev 4 201/220 ST25DV04K st25dv16k st25dv64k i2c sequences 219 table 232. polling during programing after byte write in system memory if i 2 c security session is open and register is not ro request/response frame comment master drives sda slave drives sda start aeh - device select for writing - noack 9th bit device busy start aeh - device select for writing - noack 9th bit device busy start aeh - device select for writing - ... 9th bit start aeh - device select for writing -ack 9th bit device ready programing completed stop - end of polling table 233. byte write in system memory if i 2 c security session is closed or register is ro request/response frame comment master drives sda slave drives sda start aeh - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit data - send data - noack 9th bit stop - no programming device return in standby i2c sequences ST25DV04K st25dv16k st25dv64k 202/220 docid027603 rev 4 b.3 i 2 c sequential writing and polling b.3.1 i 2 c sequential write in u ser memory and polling table 234. sequential write user memory when write operation allowed and all bytes belong to same area request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit data 0 - send data 0 - ack 9th bit data 1 - send data 1 - ack 9th bit ... - ... - ... ... data n - send data n n 256 - ack 9th bit stop - start of programming table 235. polling during programing after sequential write in user memory when write operation allowed and all bytes belong to same area. request/response frame comment master drives sda slave drives sda start a6h - device select for writing - noack 9th bit device busy start a6h - device select for writing - noack 9th bit device busy docid027603 rev 4 203/220 ST25DV04K st25dv16k st25dv64k i2c sequences 219 start a6h - device select for writing - ... 9th bit device busy start a6h - device select for writing -ack 9th bit device ready programing completed stop - end of polling table 236. sequential write in user memory when write operation allowed and crossing over area border request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit data 0 - send data 0 - ack 9th bit data 1 - send data 1 - ack 9th bit ... - ... - ... ... data n - send data n address is located in next memory area - noack 9th bit stop - no programming device return in standby table 235. polling during programing after sequential write in user memory when write operation allowed and all bytes belong to same area. (continued) request/response frame comment master drives sda slave drives sda i2c sequences ST25DV04K st25dv16k st25dv64k 204/220 docid027603 rev 4 b.3.2 i 2 c sequential write in mailbox and polling table 237. polling during programing after sequential write in user memory when write operation allowed and crossing over area border request/response frame comment master drives sda slave drives sda start a6h - device select for writing -ack 9th bit device ready no programming stop - end of polling table 238. sequential write in mailbox when mailbox is free from rf message and fast transfer mode is activated request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit address_msb - send mailbox address msb (1 byte) - ack 9th bit address_lsb - send mailbox address lsb (1 byte) - ack 9th bit data 0 - send data 0 - ack 9th bit data 1 - send data 1 - ack 9th bit ... - ... - ... ... data n - send data n n 256 - ack 9th bit stop - immediate mailbox content update docid027603 rev 4 205/220 ST25DV04K st25dv16k st25dv64k i2c sequences 219 b.4 i 2 c read current address b.4.1 i 2 c current address read in user memory table 239. polling during programing after sequential write in mailbox request/response frame comment master drives sda slave drives sda start a6h - device select for writing -ack 9th bit device ready mailbox is immediately updated stop - end of polling table 240. current byte read in user memory if read operation allowed (depending on area protection and rf user security session) request/response frame comment master drives sda slave drives sda start a7h - device select for reading - ack 9th bit data receive data located on last pointed address+1, or at address 0 after power-up, in user memory no_ack - 9th bit stop - end of reading table 241. current read in user memory if read operation not allowed (depending on area protection and rf user security session) request/response frame comment master drives sda slave drives sda start a7h - device select for reading - ack 9th bit ffh read of data not allowed st25dv release sda no_ack 9th bit stop - end of reading i2c sequences ST25DV04K st25dv16k st25dv64k 206/220 docid027603 rev 4 b.5 i 2 c random address read b.5.1 i 2 c random address read in user memory table 242. random byte read in user memory if read operation allowed (depending on area protection and rf user security session) request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit start a7h - device select for reading - ack 9th bit -datareceive data no_ack - 9th bit stop - end of reading table 243. random byte read in user memory if operation not allowed (depending on area protection and rf user security) request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit start a7h - device select for reading - ack 9th bit - ffh read of data not allowed st25dvxxx release sda no_ack - 9th bit stop - end of reading docid027603 rev 4 207/220 ST25DV04K st25dv16k st25dv64k i2c sequences 219 b.5.2 i 2 c random address read in system memory b.5.3 i 2 c random address read in dynamic registers table 244. byte read system memory (static register or i2c password after a valid present i2c password) request/response frame comment master drives sda slave drives sda start aeh - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit start afh - device select for reading - ack 9th bit -datareceive data no_ack - 9th bit stop - end of reading table 245. random byte read in dynamic registers request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit 20h - send address msb (1 byte) - ack 9th bit address_lsb - send adress lsb (1 byte) - ack 9th bit start a7h - device select for reading - ack 9th bit -datareceive data no_ack - 9th bit stop - end of reading i2c sequences ST25DV04K st25dv16k st25dv64k 208/220 docid027603 rev 4 b.6 i 2 c sequential read b.6.1 i 2 c sequential read in user memory table 246. sequential read user memory if read operation allowed (depending on area protection and rf user security session) and all bytes belong to the same area request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit start a7h0 - device select for reading - ack 9th bit - data 0 receive data 0 ack - 9th bit - data 1 receive data 1 ack - 9th bit - ... ... ... - ... - data n receive data n no_ack - 9th bit stop - end of reading table 247. sequential read user memory if read operation allowed (depending on area protection and rf user security session) but crossing area border request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit docid027603 rev 4 209/220 ST25DV04K st25dv16k st25dv64k i2c sequences 219 start a7h - device select for reading - ack 9th bit - data 0 receive data 0 ack - 9th bit - data 1 receive data 1 ack - 9th bit - ... ... ... - ... - data n receive data last address available ack - 9th bit -ffh data is located in next memory area st25dv release sda ack - 9th bit - ... ... ... - ... -ffh data is located in next memory area st25dv release sda stop - end of reading table 248. sequential read user memory if read operation allowed (depending on area protection and rf user security session) request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit start a7h - device select for reading - ack 9th bit -ffh st25dv release sda reading access not granted table 247. sequential read user memory if read operation allowed (depending on area protection and rf user security session) but crossing area border (continued) request/response frame comment master drives sda slave drives sda i2c sequences ST25DV04K st25dv16k st25dv64k 210/220 docid027603 rev 4 b.6.2 i 2 c sequential read in system memory ack - 9th bit - ... ... ... - ... -ffh st25dv release sda reading access not granted no_ack - 9th bit stop - end of reading table 248. sequential read user memory if read operation allowed (depending on area protection and rf user security session) (continued) request/response frame comment master drives sda slave drives sda table 249. sequential in read system memory (i 2 c security session open if reading i2c_pwd) request/response frame comment master drives sda slave drives sda start aeh - device select for writing - ack 9th bit address_msb - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit start af7h - device select for reading - ack 9th bit - data receive data 0 ack - 9th bit - data receive data 1 ack - 9th bit - ... ... ... - ... - data receive data n no_ack - 9th bit stop - end of reading docid027603 rev 4 211/220 ST25DV04K st25dv16k st25dv64k i2c sequences 219 b.6.3 i 2 c sequential read in dynamic registers table 250. sequential read system memory when access is not granted (i 2 c password i2c_pwd) request/response frame comment master drives sda slave drives sda start aeh - device select for writing - ack 9th bit 90h - send address msb (1 byte) - ack 9th bit address_lsb - send address lsb (1 byte) - ack 9th bit start afh - device select for reading - ack 9th bit - data receive data 0 -ffh st25dv release sda reading access is not granted ack - 9th bit - ... ... ... - ... -ffh st25dv release sda reading access is not granted no_ack - 9th bit stop - end of reading table 251. sequential read in dynamic register request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit 20h - send address msb (1 byte) - ack 9th bit dynamic register address_lsb - send address lsb (1 byte) fynamic register are located form address 2000h to 2007 - ack 9th bit start a7h - device select for reading - ack 9th bit i2c sequences ST25DV04K st25dv16k st25dv64k 212/220 docid027603 rev 4 - data receive data 0 ack - 9th bit - data receive data 1 ack - 9th bit - ... ... ... - ... - data receive data n no_ack - 9th bit stop - end of reading table 252. sequential read in dynamic register and mailbox continuously if fast transfer mode is activated request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit 20h - send address msb (1 byte) - ack 9th bit dynamic register address_lsb - send address lsb (1 byte) dynamic register are located from address 2000h to 2007h - ack 9th bit start a7h - device select for reading - ack 9th bit - data 0 receive data 0 ack - 9th bit - data 1 receive data 1 ack - 9th bit - ... ... ... - ... -data n receive data n (n 8) last dynamic register address 2007h ack - 9th bit - data n + 1 mailbox byte 0 table 251. sequential read in dynamic register (continued) request/response frame comment master drives sda slave drives sda docid027603 rev 4 213/220 ST25DV04K st25dv16k st25dv64k i2c sequences 219 b.6.4 i 2 c sequential read in mailbox ack - 9th bit - data n + 2 mailbox byte 1 ack - 9th bit - ... ... ... - ... - data n + i mailbox byte i (i < 256) no_ack - 9th bit stop - end of reading table 252. sequential read in dynamic register and mailbox continuously if fast transfer mode is activated (continued) request/response frame comment master drives sda slave drives sda table 253. sequential in mailbox if fast transfer mode is activated request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit 20h or 21h - send address msb (1 byte) 2007h < @ 2108h - ack 9th bit address_lsb - send address lsb (1 byte) 2007h < @ 2108h - ack 9th bit start a7h - device select for reading - ack 9th bit - data 0 receive data 0 ack - 9th bit - data 1 receive data 1 ack - 9th bit - ... ... ... - ... - data n receive data n no_ack - 9th bit stop - end of reading i2c sequences ST25DV04K st25dv16k st25dv64k 214/220 docid027603 rev 4 table 254. sequential read in mailbox if fast transfer mode is not activated request/response frame comment master drives sda slave drives sda start a6h - device select for writing - ack 9th bit 20h or 21h - send address msb (1 byte) 2007h < @ 2108h - ack 9th bit address_lsb - send address lsb (1 byte) 2007h < @ 2108h - ack 9th bit start a7h - device select for reading - ack 9th bit - ffh st25dvxxx release sda ack - 9th bit - ffh st25dvxxx release sda ack - 9th bit - ... ... ... - ... - ffh st25dvxxx release sda no_ack - 9th bit stop - end of reading docid027603 rev 4 215/220 ST25DV04K st25dv16k st25dv64k i2c sequences 219 b.7 i 2 c password relative sequences b.7.1 i 2 c write password table 255. write password when i 2 c security session is already open and fast transfer mode is not activated request/response frame comment master drives sda slave drives sda start aeh - device select for writing - ack 9th bit 09h - send i2c_pwd msb address - ack 9th bit 00h - send i2c_pwd lsb address - ack 9th bit i2c_pwd_byte_7 - send i2c_pwd msb - ack 9th bit i2c_pwd_byte_6 data 0 send data - ack 9th bit ... - ... - ... ... i2c_pwd_byte_0 - send i2c_pwd lsb - ack 9th bit 07h - write password command - ack 9th bit i2c_pwd_byte_7 - send i2c_pwd msb - ack 9th bit i2c_pwd_byte_6 data 0 send data - ack 9th bit ... - ... - ... ... i2c_pwd_byte_0 - send i2c_pwd lsb - ack 9th bit stop -start of i 2 c password programming i2c sequences ST25DV04K st25dv16k st25dv64k 216/220 docid027603 rev 4 b.7.2 i 2 c present password table 256. write password when i 2 c security session is not open or fast transfer mode activated request/response frame comment master drives sda slave drives sda start aeh - device select for writing - ack 9th bit 09h - send i2c_pwd msb address - ack 9th bit 00h - send i2c_pwd lsb address - noack 9th bit stop - no pwd programming device return in standby present password (whatever status of i 2 c security session or fast transfer mode) request/response frame comment master drives sda slave drives sda start aeh - device select for writing - ack 9th bit 09h - send i2c_pwd msb address - ack 9th bit 00h - send i2c_pwd lsb address - ack 9th bit i2c_pwd_byte_7 - send i2c_pwd msb - ack 9th bit i2c_pwd_byte_6 data 0 send data - ack 9th bit ... - ... - ... ... i2c_pwd_byte_0 - send i2c_pwd lsb - ack 9th bit 09h - present password command - ack 9th bit i2c_pwd_byte_7 - send i2c_pwd msb - ack 9th bit i2c_pwd_byte_6 - send data docid027603 rev 4 217/220 ST25DV04K st25dv16k st25dv64k i2c sequences 219 - ack 9th bit ... - ... - ... ... i2c_pwd_byte_0 - send i2c_pwd lsb - ack 9th bit stop - st25dv with active i2c_pwd. result is immediate. present password (whatever status of i 2 c security session or fast transfer mode) request/response frame comment master drives sda slave drives sda revision history ST25DV04K st25dv16k st25dv64k 218/220 docid027603 rev 4 revision history table 257. document revision history date revision changes 23-feb-2017 1 initial release. 20-sep-2017 2 updated: ? features ? section 4: memory management ? section 5: st25dvxxx specific features ? section 5.6.4: system memory protection ? section 6.4.2: i 2 c sequential write ? section 6: i 2 c operation ? section 7: rf operations ? section 9.1: maximum rating ? ta ble 121: get system info response format error_flag is not set ? ta ble 203: absolute maximum ratings ? ta ble 205: ac test measurement conditions ? ta ble 207: i 2 c dc characteristics up to 85c ? ta ble 209: i 2 c ac characteristics up to 85c ? ta ble 211: gpo dc characteristics up to 85c ? ta ble 214: rf characteristics ? ta ble 215: operating conditions ? ta ble 217: tssop8 ? 8-lead thin shrink small outline, 3 x 6.4 mm, 0.65 mm pitch, package mechanical data ? ta ble 221: ordering information scheme ? figure 30: i 2 c present password sequence ? figure 31: i 2 c write password sequence ? figure 79: tssop8 ? 8-lead thin sh rink small outline, 3 x 6.4 mm, 0.65 mm pitch, package outline added: ? ta ble 122: memory size ? ta ble 204: i 2 c operating conditions ? ta ble 208: i 2 c dc characteristics up to 125c ? ta ble 210: i 2 c ac characteristics up to 125c ? ta ble 212: gpo dc characteristics up to 125c 04-oct-2017 3 updated: ? features ? section 10: package information added: ? nfc certified logo docid027603 rev 4 219/220 ST25DV04K st25dv16k st25dv64k revision history 219 19-dec-2017 4 added: ? figure 4: st25dvxxx 10-ball wlcsp package connections with cmos interrupt output (gpo) ? section 10.5: wlcsp10 package information ? ta ble 220: wlcsp - 10 balls, 1. 649x1.483 mm, 0.4 mm pitch, wafer level chip scale mechanical data ? figure 82: wlcsp - 10 balls, 1.649x1.483 mm, 0. 4 mm pitch, wafer level chip scale package outline ? figure 83: wlcsp - 10 balls, 1.649x1.483 mm, 0. 4 mm pitch, wafer level chip scale recommended footprint updated: ? features ? section 1: description ? section 2.5: energy harvestin g analog output (v_eh) ? section 5.3.2: energy harvest ing feature description ? figure 21: st25dvxxx, arbitrat ion between rf and i 2 c ? section 6.4.1: i 2 c byte write ? section 6.4.2: i 2 c sequential write ? ta ble 203: absolute maximum ratings ? ta ble 204: i 2 c operating conditions ? ta ble 221: ordering information scheme deleted: ? device summary table 257. document re vision history (continued) date revision changes ST25DV04K st25dv16k st25dv64k 220/220 docid027603 rev 4 3 important notice ? please read carefully stmicroelectronics nv and its subsidiaries (?st?) reserve the right to make changes, corrections, enhancements, modifications, and improvements to st products and/or to this document at any time without notice. purchasers should obtain the latest relevant in formation on st products before placing orders. st products are sold pursuant to st?s terms and conditions of sale in place at the time of o rder acknowledgement. purchasers are solely responsible for the choice, selection, and use of st products and st assumes no liability for application assistance or the design of purchasers? products. no license, express or implied, to any intellectual property right is granted by st herein. resale of st products with provisions different from the information set forth herein shall void any warranty granted by st for such product. st and the st logo are trademarks of st. all other product or service names are the property of their respective owners. information in this document supersedes and replaces information previously supplied in any prior versions of this document. ? 2017 stmicroelectronics ? all rights reserved |
Price & Availability of ST25DV04K
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |